Regression tests: EXIT STATUS: 666
Regression status reports list the following run output for some tests of my lib in CWPro8: EXIT STATUS: 666 And nothing more (see for instance http://tinyurl.com/2e56z) Anyone has a clue what this is about? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
Joaquín Mª López Muñoz writes:
Regression status reports list the following run output for some tests of my lib in CWPro8:
EXIT STATUS: 666
And nothing more (see for instance http://tinyurl.com/2e56z) Anyone has a clue what this is about?
That's what you get when a test was terminated by our build/run monitor; the most likely reasons are: 1) It was running for too long. 2) It failed with some kind of run-time assertion/exception, _showing a dialog_, and got killed as the result. Obviously, the diagnostics could be better. It's on our todo list. -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy ha escrito:
Joaquín Mª López Muñoz writes:
Regression status reports list the following run output for some tests of my lib in CWPro8:
EXIT STATUS: 666
And nothing more (see for instance http://tinyurl.com/2e56z) Anyone has a clue what this is about?
That's what you get when a test was terminated by our build/run monitor; the most likely reasons are:
1) It was running for too long. 2) It failed with some kind of run-time assertion/exception, _showing a dialog_, and got killed as the result.
Obviously, the diagnostics could be better. It's on our todo list.
Well, I've just tried the whole multi_index test suite in the evaluation version of CWPro 9.2 for Windows, and everything works OK (and does not get stalled or anything). So, I don't have a clue. If anyone with access to CWPro 8.3 Win volunteers to try to reproduce this behavior manually, my eternal gratitude will go to h(er|im). Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
participants (2)
-
Aleksey Gurtovoy -
Joaquín Mª López Muñoz