The following test timed out in the JDK26 CI:

java/util/concurrent/forkjoin/AsyncShutdownNowInvokeAnyRace.java

Here's a snippet from the log file:

#section:testng
----------messages:(11/369)----------
command: testng AsyncShutdownNowInvokeAnyRace
reason: User specified action: run testng AsyncShutdownNowInvokeAnyRace
started: Sat Oct 04 04:41:42 UTC 2025
Mode: agentvm
Agent id: 9
Process id: 50036
Timeout signalled after 120 seconds
Timeout information:
--- Timeout information end.
finished: Sat Oct 04 04:49:38 UTC 2025
elapsed time (seconds): 475.585
----------configuration:(12/1135)*----------

<snip>

----------System.out:(7/288)----------
test AsyncShutdownNowInvokeAnyRace.testInvokeAny(): success [133293ms]

===============================================
java/util/concurrent/forkjoin/AsyncShutdownNowInvokeAnyRace.java
Total tests run: 1, Passes: 1, Failures: 0, Skips: 0
===============================================

----------System.err:(3/38)----------

JavaTest Message: Test complete.

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


According to this line in the stdout log:

test AsyncShutdownNowInvokeAnyRace.testInvokeAny(): success [133293ms]

This test finished in 133.29 seconds which is past the default 120 seconds
timeout. The total elapsed time for the test execution is:

elapsed time (seconds): 475.585

so almost 480 seconds which is what the old total timeout value
would have been with a TimeoutFactor value of 4.

I don't know if the agent thread got stuck after this test passed,
but it clearly needs a little more time than 120 seconds.