JDK-8203393 : com/sun/jdi/JdbMethodExitTest.sh and JdbExprTest.sh fail due to timeout
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-05-18
  • Updated: 2022-06-30
  • Resolved: 2018-08-27
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.
JDK 11 JDK 12
11.0.10-oracleFixed 12 b09Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
[Note: This CR was created out of JDK-8171483, which discussed multiple issues and became to cluttered to followed.] 

When running on solaris-sparc, this test often times out. When it passes, stdout ends with:

main[1]
--Done: test passed

When it fails:

Timeout refired 1200 times

Before that there is quite a bit of logging for breakpoints, method exits, and stepping. They are exactly the same for the pass and failed cases. So it looks like for the most part the test is running properly, but just not terminating.

On Solaris, stderr ends with the following whether or not it passes:

--Finish execution with sending "quit" command to JDB
--Sending cmd: quit
--Quit cmd was sent
--waitForFinish: Waiting for mydojdbCmds() to finish

On linux it's a bit different. I see:

--Finish execution with sending "quit" command to JDB
--Sending cmd: quit
--Quit cmd was sent
--waitForFinish: Waiting for all processes to finish

waitForFinish output comes from ShellScaffold.sh, and it is different for Solaris. The Solaris logic is much more complicated than linux, which just has to do a simple "wait" command.

Note, these tests will be converted from shell scripts to java as part of  JDK-8179318. That should resolve this issue.
Comments
Fix Request (11u) This backport improves testing and matches the codebases better (I see 11.0.10-oracle). Patch applies cleanly to 11u, affected com/sun/jdi tests pass in {fastdebug,release}. This bunch contains a rewrite and a few follow-ups: JDK-8209109, JDK-8209517, JDK-8209605, JDK-8203393.
25-08-2020

URL: http://hg.openjdk.java.net/jdk/jdk/rev/2af74a1edb11 User: amenkov Date: 2018-08-27 23:45:41 +0000
27-08-2018