-
Enhancement
-
Resolution: Fixed
-
P4
-
12
-
b13
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8252165 | 11.0.10-oracle | Jagjot Singh | P4 | Resolved | Fixed | b01 |
JDK-8252436 | 11.0.9 | Alex Menkov | P4 | Resolved | Fixed | b06 |
This enhancement suggestion is the same as what was done for JDK-8210118, but in this case it is applied to the test/jdk version of waitForPrompt() instead of the nsk/jdb version.
Note forJDK-8210118 the dumping of the pending reply was done in receiveReply() after waitForPrompt() timed out, but it might be more appropriate to do it in waitForPrompt(). I had considered this for JDK-8210118, but only after having already implemented and extensively tested the fix in receiveReply(), so I just left the code there.
Note for
- backported by
-
JDK-8252165 [TESTBUG] lib.jdb.Jdb.waitForPrompt() should clarify which output is the pending reply after a timeout
- Resolved
-
JDK-8252436 [TESTBUG] lib.jdb.Jdb.waitForPrompt() should clarify which output is the pending reply after a timeout
- Resolved
- relates to
-
JDK-8210725 com/sun/jdi/RedefineClearBreakpoint.java fails with waitForPrompt timed out after 60 seconds
- Resolved
-
JDK-8210118 better jdb test diagnostics when getting "Prompt is not received during ... milliseconds" failures
- Resolved