The following test timed out in the JDK16 CI:

vmTestbase/vm/mlvm/indy/stress/jdi/breakpointInCompiledCode/Test.java

Here's a snippet from the log file:

#section:main
----------messages:(6/1173)----------
command: main vm.mlvm.indy.stress.jdi.breakpointInCompiledCode.Test -verbose -arch=linux-x64 -waittime=5 -debugee.vmkind=java -transport.address=dynamic -debugger.debuggeeClass vm.mlvm.share.jdi.IndyDebuggee -debuggee.iterations 20000 -debugee.vmkeys="-XX:MaxRAMPercentage=6 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/983c483a-6907-44e0-ad29-98c7183575e2-S77107/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/9e5b7e34-f0e9-4147-baab-40c6b7e81520/runs/1d4b7b15-aa28-47ab-9868-ec43fdfbf5d2/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_vm_mlvm/tmp -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:-TieredCompilation"
reason: User specified action: run main/othervm vm.mlvm.indy.stress.jdi.breakpointInCompiledCode.Test -verbose -arch=${os.family}-${os.simpleArch} -waittime=5 -debugee.vmkind=java -transport.address=dynamic -debugger.debuggeeClass vm.mlvm.share.jdi.IndyDebuggee -debuggee.iterations 20000 -debugee.vmkeys="${test.vm.opts} ${test.java.opts}"
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 528.513
----------configuration:(0/0)----------
----------System.out:(23/2359)*----------
binder> VirtualMachineManager: version 16.0
binder> Finding connector: default
binder> LaunchingConnector:
binder> name: com.sun.jdi.CommandLineLaunch
binder> description: Launches target using Sun Java VM command line and attaches to it
binder> transport: com.sun.tools.jdi.SunCommandLineLauncher$2@28afe440
binder> Connector arguments:
binder> home=/opt/mach5/mesos/work_dir/jib-master/install/jdk-16+30-2102/linux-x64-debug.jdk/jdk-16/fastdebug
binder> vmexec=java
binder> options=-XX:MaxRAMPercentage=6 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/983c483a-6907-44e0-ad29-98c7183575e2-S77107/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/9e5b7e34-f0e9-4147-baab-40c6b7e81520/runs/1d4b7b15-aa28-47ab-9868-ec43fdfbf5d2/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_vm_mlvm/tmp -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:-TieredCompilation
binder> main=vm.mlvm.share.jdi.IndyDebuggee \u0000-verbose\u0000 \u0000-arch=linux-x64\u0000 \u0000-waittime=5\u0000 \u0000-debugee.vmkind=java\u0000 \u0000-transport.address=dynamic\u0000 \u0000-debugger.debuggeeClass\u0000 \u0000vm.mlvm.share.jdi.IndyDebuggee\u0000 \u0000-debuggee.iterations\u0000 \u000020000\u0000 \u0000-debugee.vmkeys="-XX:MaxRAMPercentage=6 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/983c483a-6907-44e0-ad29-98c7183575e2-S77107/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/9e5b7e34-f0e9-4147-baab-40c6b7e81520/runs/1d4b7b15-aa28-47ab-9868-ec43fdfbf5d2/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_vm_mlvm/tmp -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:-TieredCompilation"\u0000 \u0000-pipe.port=39169\u0000
binder> quote=\u0000
binder> suspend=true
binder> Launching debugee
binder> Waiting for VM initialized
Initial VMStartEvent received: VMStartEvent in thread main
### TRACE 1: Breakpoint for method bootstrap was hit 1 times. OK.
### TRACE 1: Breakpoint for method runDebuggee was hit 1 times. OK.
### TRACE 1: Breakpoint for method indyWrapper was hit 1 times. OK.
### TRACE 1: Breakpoint for method target was hit 1 times. OK.
### TRACE 1: Breakpoint for method stop was hit 1 times. OK.
Timeout refired 480 times
### TRACE 1: TEST PASSED
----------System.err:(0/0)----------
----------rerun:(40/9362)*----------


It looks like the test PASSED while the timeout handler was running.
It's using the default 2 minute/120 second timeout value and with the
default timeoutFactor of 4, that gives us a total timeout value of
8 minutes/480 seconds.

Looks like it took just a little longer:

elapsed time (seconds): 528.513

so perhaps a timeout value of 180 seconds would be
a good choice.