This was buggy and based on deprecated SDL features that will not
continue to be available. aquileia wrote us a very nice windows
port of the run_wml_tests bash script, so for windows mac and
linux we should now be able to run the unit tests as desired.
Maybe someday built-in timeouts can be supported using boost
process library, if that ever materializes.
This is to combat what are apparently transient timeout faults
where the travis workers choke on running ./test and never
actually start the process... it seems not even to get to the
"running 140 tests" message when it ends with error code 200.
With the change to --log-strict, it's not necessary to rerun with
strict mode off, so we can get rid of part of the old system.
Feel free to revert this is you don't want travis to require all
unit tests to pass as part of the build.
- travis runs tests not in verbose mode,
*but* if there is a failure,
then it runs in very verbose mode, with strict mode off, to get
errors reported in the travis log.
- run_wml_tests points out that if you don't run in strict mode,
some tests may not fail as expected, so the count at the end
may differ
Adds an option to the new wml test script, to use the unix
timeout command instead of wesnoth's built-in one. This is because
the built-in one is very slightly unreliable... there's a reason
killthread was deprecated in SDL unfortunately. Will leave it for
UMC but on travis will replace with unix timeout.
The unix timeout one seems consistent enough that I will enable
the empty_test timeout check for travis.
Also, adds a help listing to the wml test script.
Also, redirect some output from cout to cerr in the game...
this somewhat breaks the old script.
The old script is renamed .old
Travis points to the new script.
