22 Jun
2016
22 Jun
'16
5:26 p.m.
2016-06-21 9:23 GMT+03:00 deloptes <deloptes(a)gmail.com>om>:
Fat-Zer wrote:
So, are you ok to fixing and testing bunches of stuff in
tdelibs&tdebase? If so, I start the cmake stuff...
I don't want either to do this quite boring and low-requred job all by
myself or to stuck with the job half-done...
Some notes to be taken into account:
1) There are two types of checks:
- "make check" builds test snippets that are required to be run by
the user and see if they produce correct output
- "make test" runs those few which are intended to be run as part
of automatic system
2) The programs themselves are broken (mostly they have same mistake
related to changed TDEApplication constructor signature)
This sounds good. Thank you!
I may fix the cmake stuff for you, if you will
repair the programs
themselves (95% is to change 1 line, but I wouldn't trust in that
particular case to a script) and do the testing (at least make sure
that all checks are getting run and won't crash instantly).
Indeed I have noticed this. An example is the tdepim calendar tests I tried
recently. When there is DTSTART; DATE: 20030901, I get in the test result
file DTSTART: 201606......T.....Z
It could be we broke something by fixing the null date/time issue
Also for doing it right I will follow the order:
tdelibs -> tdebase ->
tdepim.
This is also a good hint. Thanks