The following test timed out in the JDK16 CI:

compiler/jsr292/RedefineMethodUsedByMultipleMethodHandles.java

Here's a snippet from the log file:

#section:main
----------messages:(7/536)----------
command: main -Djdk.attach.allowAttachSelf compiler.jsr292.RedefineMethodUsedByMultipleMethodHandles
reason: User specified action: run main/othervm -Djdk.attach.allowAttachSelf compiler.jsr292.RedefineMethodUsedByMultipleMethodHandles
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules java.base,java.compiler,java.instrument,java.management,jdk.attach --add-exports java.base/jdk.internal.org.objectweb.asm=ALL-UNNAMED
Timeout information:
--- Timeout information end.
elapsed time (seconds): 556.213
----------configuration:(4/163)----------
Boot Layer
  add modules: java.base java.compiler java.instrument java.management jdk.attach
  add exports: java.base/jdk.internal.org.objectweb.asm ALL-UNNAMED

----------System.out:(5/165)----------
fooMH1.invoke = foo
fooMH2.invoke = foo
Timeout refired 480 times
redefining class compiler.jsr292.RedefineMethodUsedByMultipleMethodHandles$Foo
fooMH1.invoke = foo
----------System.err:(1/15)----------
STATUS:Passed.
----------rerun:(36/6627)*----------

Since "STATUS:Passed." was printed to System.err, the
test actually passed while the JTREG timeout handler
was running. Perhaps all this test needs is a slightly
longer default timeout value (currently using the default
of 120 seconds/2 minutes). With the timeoutFactor of 4,
the total timeout for this test was 480 seconds/8 minutes
and the elapsed time was 556.213.