Yet another case where the 120s timeout after the timeout factor change seems inadequate to account for concurrnet loading whilst the test is running.

Log shows nothing:

----------System.err:(15/670)----------
STARTED MultiReleaseJarAwareSJFM::test '[1] , 8'
SUCCESSFUL MultiReleaseJarAwareSJFM::test '[1] , 8' [6338ms]
STARTED MultiReleaseJarAwareSJFM::test '[2] 8, 8'
SUCCESSFUL MultiReleaseJarAwareSJFM::test '[2] 8, 8' [93ms]
STARTED MultiReleaseJarAwareSJFM::test '[3] 9, 9'
SUCCESSFUL MultiReleaseJarAwareSJFM::test '[3] 9, 9' [185ms]
STARTED MultiReleaseJarAwareSJFM::test '[4] runtime, 26'
SUCCESSFUL MultiReleaseJarAwareSJFM::test '[4] runtime, 26' [108ms]

[ JUnit Containers: found 5, started 5, succeeded 5, failed 0, aborted 0, skipped 0]
[ JUnit Tests: found 4, started 4, succeeded 4, failed 0, aborted 0, skipped 0]


JavaTest Message: Test complete.

result: Error. "junit" action timed out with a timeout of 120 seconds on agent 15

but top shows:

   PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 298432 mach5-r+ 20 0 4600316 449428 48256 S 190.9 1.8 1:16.92 java
 265854 mach5-r+ 20 0 5412616 1.8g 99584 S 163.6 7.6 23:39.68 java
 300365 mach5-r+ 20 0 3952080 158840 46528 S 154.5 0.6 0:05.40 java
 287861 mach5-r+ 20 0 5283468 1.6g 88576 S 109.1 6.7 23:59.17 java
 265668 mach5-r+ 20 0 4746368 777752 52480 S 100.0 3.2 5:00.34 java
 265920 mach5-r+ 20 0 6013316 1.8g 64640 S 100.0 7.6 25:33.38 java
 295788 mach5-r+ 20 0 4800224 981.5m 46464 S 90.9 4.1 6:57.02 java