Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8234195

ClhsdbCDSJstackPrintAll.java failed due to "RuntimeException: 'Java Stack Trace for main' missing from stdout/stderr"

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: 14
    • Fix Version/s: None
    • Component/s: hotspot
    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      windows

      Description

      The following test failed in the JDK14 CI:

      serviceability/sa/ClhsdbCDSJstackPrintAll.java

      Here's a snippet from the log file:

       LingeredApp stdout: [];
       LingeredApp stderr: []
       LingeredApp exitValue = 0
      java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'Java Stack Trace for main' missing from stdout/stderr

      at ClhsdbCDSJstackPrintAll.main(ClhsdbCDSJstackPrintAll.java:118)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.base/java.lang.reflect.Method.invoke(Method.java:564)
      at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
      at java.base/java.lang.Thread.run(Thread.java:833)
      Caused by: java.lang.RuntimeException: 'Java Stack Trace for main' missing from stdout/stderr

      at jdk.test.lib.process.OutputAnalyzer.shouldMatch(OutputAnalyzer.java:306)
      at ClhsdbLauncher.runCmd(ClhsdbLauncher.java:149)
      at ClhsdbLauncher.run(ClhsdbLauncher.java:197)
      at ClhsdbCDSJstackPrintAll.main(ClhsdbCDSJstackPrintAll.java:114)
      ... 6 more

      JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'Java Stack Trace for main' missing from stdout/stderr

      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'Java Stack Trace for main' missing from stdout/stderr
      ----------rerun:(36/4955)*----------


      The log file shows output that looks like this:

      Thread 16 Address: 0x0000006e7000f000

      Java Stack Trace for Service Thread
      Thread state = BLOCKED

      Thread 17 Address: 0x0000006e70012000

      Java Stack Trace for Notification Thread
      Thread state = BLOCKED

      Thread 19 Address: 0x0000006e7004c000

      Java Stack Trace for Common-Cleaner
      Thread state = BLOCKED
       - public final native void wait(long) @0x0000000800010e50 @bci = 0, pc = 0x0000006e35ac2ef7 (Interpreted)
      - waiting on <0x000000043fc9dba8> (a java.lang.ref.ReferenceQueue$Lock)
       - public java.lang.ref.Reference remove(long) [signature (J)Ljava.lang.ref.Reference<+TT;>;] @0x000000080035ef58 @bci = 59, line = 155, pc = 0x0000006e35aba3b3, oop = 0x000000043fc9db88 (Interpreted)
      - locked <0x000000043fc9dba8> (a java.lang.ref.ReferenceQueue$Lock)
       - public void run() @0x000000080029ab80 @bci = 65, line = 148, pc = 0x0000006e35aba100, oop = 0x000000043fc9db68 (Interpreted)

       - public void run() @0x0000000800131df8 @bci = 11, line = 833, pc = 0x0000006e35aba3f8, oop = 0x000000043fc9e578 (Interpreted)

       - public void run() @0x00000008002971e0 @bci = 20, line = 134, pc = 0x0000006e35aba3b3, oop = 0x000000043fc9e578 (Interpreted)

      and I don't see an entry for 'Java Stack Trace for main'.


      This is a Tier1 test failure. Normally this failure would start at P2.
      However, the next build ID after this one does not show this error.
      A search of Mach5 history shows a total of two failures in the
      JDK14 CI and the other one does not match this one. So... I'm
      starting this bug at P3.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dcubed Daniel Daugherty
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: