You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected make test to pass all tests, and hopefully well within 4 hours.
Screenshots
Here is the end of build/Testing/Temporary/LastTest.log:
ESTID=66869 running in /tmp/comdb2/tests/test_66869 systable_locking_extralock_generated 13/362
!systable_locking_extralock_generated: creating db systablelockingextralockgenerated66869
!systable_locking_extralock_generated: starting single node
!systable_locking_extralock_generated: waiting until ready
!systable_locking_extralock_generated: started running with timeout 30m at 2020-08-07 13:44:51
!systable_locking_extralock_generated: finished running with timeout 30m at 2020-08-07 14:14:51
!systable_locking_extralock_generated: timeout (logs in /tmp/comdb2/tests/test_66869/logs/systablelockingextralockgenerated66869.testcase)
!systable_locking_extralock_generated: stopping
make[2]: *** [/tmp/comdb2/tests/testcase.mk:59: test] Error 124
make[1]: *** [Makefile:89: systable_locking_extralock_generated] Error 2
<end of output>
Test time = 14460.52 sec
----------------------------------------------------------
Test Failed.
"all-tests" end time: Aug 07 14:18 BST
"all-tests" time elapsed: 04:01:00
----------------------------------------------------------
End testing: Aug 07 14:18 BST
However the testcase log file does not seem to contain any error information:
The test in question timed out: !systable_locking_extralock_generated: timeout (logs in /tmp/comdb2/tests/test_66869/logs/systablelockingextralockgenerated66869.testcase)
the make all-tests method runs all tests sequentially and on an timeout (or error) will stop running any further tests. Please see comments to #2391 about ways to run in parallel and not stop at the first error encountered (basically make -k).
We have improved the detection when a test is stuck and should be better handling this scenario past its timeout (which in this case was 30min), fail this particular test and move on to the next.
make test fails with error 124 after four hours , in the testcase systablelockingextralockgenerated .
I don't think #2311 helps.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected make test to pass all tests, and hopefully well within 4 hours.
Screenshots
Here is the end of build/Testing/Temporary/LastTest.log:
However the testcase log file does not seem to contain any error information:
Environment (please complete the following information):
Ubuntu Linux 20.04.1 AMD64
The text was updated successfully, but these errors were encountered: