JDK-8367615 : JDI tests are timing out and passing
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 26
  • Priority: P4
  • Status: New
  • Resolution: Unresolved
  • Submitted: 2025-09-15
  • Updated: 2025-09-15
Related Reports
Relates :  
JDK-8260555 - Change the default TIMEOUT_FACTOR from 4 to 1
Description
Three timeouts on the same machine in the same test run - see JDK-8367614 for the other failure.

vmTestbase/nsk/jdi/ReferenceType/instances/instances005/instances005.java

[19:11:55.937] debugee.stderr> [19:11:55.937] Debuggee nsk.share.jdi.HeapwalkingDebuggee : sending the command: ready
Timeout signalled after 120 seconds
[19:14:2.762] debugee.stderr> [19:14:2.762] Debuggee: received the command: quit
[19:14:2.762] debugee.stderr> [19:14:2.762] Debuggee: exiting
[19:14:4.875] Debuggee's process finished with status: 95
[19:14:4.875] TEST PASSED

vmTestbase/nsk/jdi/ObjectReference/referringObjects/referringObjects004/referringObjects004.java

Timeout signalled after 120 seconds
[19:12:48.382] debugee.stderr> [19:12:48.382] Debuggee: received the command: quit
[19:12:48.382] debugee.stderr> [19:12:48.382] Debuggee: exiting
[19:12:50.665] Debuggee's process finished with status: 95
[19:12:50.665] TEST PASSED

Concurrent activity on the test machines seems to be triggering the timouts.
Comments
Actually there is a bit of similarity with the timeout in JDK-8367614 . All the failures have a similar pattern at the end: [19:10:39.928] debugee.stderr> [19:10:39.928] Debuggee nsk.share.jdi.HeapwalkingDebuggee : sending the command: ready Timeout signalled after 120 seconds [19:12:48.382] debugee.stderr> [19:12:48.382] Debuggee: received the command: quit [19:12:48.382] debugee.stderr> [19:12:48.382] Debuggee: exiting [19:12:50.665] Debuggee's process finished with status: 95 So the debuggee indicates it is ready, and then it takes two minutes for the quit to arrive, which is probably being triggered by the timeout.
15-09-2025
I don't think the timeout in JDK-8367614 is related. I believe with JDK-8367614 it is due to the test failing due to an unexpected exception, and then timing out due to the debugger and debuggee getting out of sync.
15-09-2025