Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
N/A
-
None
Description
As seen in some aarch64-debian-sid jobs like.
|
https://buildbot.mariadb.org/#/builders/138/builds/6182 |
innodb.temporary_table 'innodb' w6 [ pass ] 13132
|
stress.ddl_myisam w7 [ pass ] 33449
|
 |
command timed out: 600 seconds without output running [b'sh', b'-c', b'cd mysql-test && exec perl mysql-test-run.pl --verbose-restart --force --retry=3 --max-save-core=1 --max-save-datadir=1 --max-test-fail=20 --mem --parallel=$(expr 25 \\* 2) '], attempting to kill
|
process killed by signal 9
|
This hard kill off by buildbot give no indication as to which test it is currently running.
The mtr testcase-timeout=MINUTES Max test case run time (default 15) should always be less than this. Setting testcase-timeout=8 and keeping the 600 second ( 10 minute) output timeout should allow mtr to kill off stalled tests and report their failure.
