#1690: The test system should treat a nonzero exit code from Cactus as a failure
| Reporter: | Ian Hinder |
| Status: | resolved |
| Milestone: | |
| Version: | development version |
| Type: | bug |
| Priority: | minor |
| Component: | Cactus |
Changes (by Roland Haas):
| status: | resolved (was open) |
The test system seems to ignore the fact that Cactus exits with a nonzero exit code. It displays
Cactus exited with error code 1
Please check the logfile...
No files created in test directory
Success: 0 files identical
And in the summary at the end, it treats this as a passing test. In this case, there were no test reference files and no files output, because the test (by design) does not produce any data, it just aborts if the test fails.
Keyword:
Comment (by Roland Haas):
Applied as git hash cbbed86e "Cactus: Fixed bug where par files which core dumped would pass" of cactus
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1690/the-test-system-should-treat-a-nonzero