[CMake] random BAD_COMMAND error on ctest

[BILODEAU Andre]

Installed cmake 2.8.4...  Always the same problem of apparently random failures.

There are 2 sets of tests:
1- The first 17 tests use a driver for calling the tested program. There are random failures.
2- The other 13 test programs are called directly. Only the program that internally performs unix fork/exec randomly fails.

For the following tests, I will go back to cmake 2.8.10.2, start from a simple test driver, and add complexity till the problem appears.

-----Message d'origine-----
De : Eric Noulard [mailto:eric.noulard at gmail.com] 
Envoyé : mercredi 9 janvier 2013 08:21
À : BILODEAU Andre
Cc : CMake ML
Objet : Re: [CMake] random BAD_COMMAND error on ctest

Andre please do not drop the ML address.

2013/1/9 BILODEAU Andre <andre.bilodeau at safran-engineering.com>:
> New test:
> I just replaced my test driver by a simple stub, which is run for each of the tests from test_01 to test_17:
>
> #!/bin/ksh
> exit 0
>
> All the tests run without error.
>
> That seems strange because the test driver that the stub replaces works well on autotools or in stand-alone mode, either under cygwin or Mac OS X. The real test driver activate programs, reads and writes files etc., but cmake should only "see" that it exits with status 0.

Yes this weird but this may be some time dependent race, may be you can try to put a 'sleep' in the previous stub.
Moreover from your report and the message from Allen it reallly seems to be a cygwin specific issue.

May be if one of you can craft a repeatable testcase which exhibit the issue it would be nice to file this to the bug tracker.

I won't be able to help you for that since I'm no cygwin user and I have no time to work on this.

Good luck though.
--
Erk
Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org