The following test timed out in the JDK26 CI:

tools/javac/completionDeps/DepsAndAnno.java

Here's a snippet from the log file:

#section:main
----------messages:(10/499)----------
command: main DepsAndAnno
reason: User specified action: run main/othervm/timeout=10 DepsAndAnno
started: Mon Sep 15 12:19:25 UTC 2025
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules jdk.compiler --add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED
Process id: 3074007
Timeout information:
--- Timeout information end.
finished: Mon Sep 15 12:19:50 UTC 2025
elapsed time (seconds): 25.063
----------configuration:(5/196)----------
Boot Layer
  add modules: jdk.compiler
  add exports: jdk.compiler/com.sun.tools.javac.api ALL-UNNAMED
               jdk.compiler/com.sun.tools.javac.main ALL-UNNAMED

----------System.out:(1/35)----------
Timeout signalled after 10 seconds
----------System.err:(1/15)----------
STATUS:Passed.
----------rerun:(50/7922)*----------

So the test timed out at 10 seconds, but PASSed while the timeout
handler was running.

The test is invoked like this:

    run main/othervm/timeout=10 DepsAndAnno

and that 10 second timeout used to be 40 seconds with the
old timeout factor:

JDK-8260555 Change the default TIMEOUT_FACTOR from 4 to 1

Based on this bit from the test's log file:

    elapsed time (seconds): 25.063

and this bit from the task's stdout log:

    -concurrency:4

It looks like 10 seconds is not enough time when
run with a concurrency of 4.