JDK-8210118 : better jdb test diagnostics when getting "Prompt is not received during ... milliseconds" failures
- Type: Enhancement
- Component: core-svc
- Sub-Component: debugger
- Affected Version: 12
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-08-28
- Updated: 2018-09-14
- Resolved: 2018-08-31
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 12 |
|---|
12 b10Fixed  |
Related Reports
|
Relates :
|
Description
The following failure is quite common among the jdb tests: "Prompt is not received during ... milliseconds" It is produced when receiveReply() calls waitForPrompt() and the prompt was never detected. Usually there is reply data available when this happens, and printing it is very useful for debugging. See the description of JDK-8208468 for example. Dumping the pending reply made the cause of the failure obvious. receiveReply() should be modified as indicated in JDK-8208468 to dump the pending reply when waitForPrompt() fails.