Bug in testframework

When tests timeout, the testframework sometimes seems to think that they returned UNSAT instead of viewing this as a timeout.

E.g., in debug

Failed: ModelExpansion/MXsatTest.DoesMX/49
Testing /home/bartb/software/idp/tests/mx/satmx/ineq_packing_issue.idp
Out of resources
Mx took 12 sec
Found UNSAT, expected SAT.
/home/bartb/software/idp/tests/TestUtils.cpp:30: Failure
Value of: result
  Actual: failed
Expected: Status::SUCCESS
Which is: success

Comments (0)