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

nsk/jdi tests fail with unexpected com.sun.jdi.InvocationException

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: core-svc
    • Labels:
    • Subcomponent:
    • CPU:
      sparc
    • OS:
      solaris_11

      Description

      nsk/jdi/ObjectReference/invokeMethod/invokemethod008 fails in hs nightly with the following:

      [2016-03-29T04:16:22.17] # ERROR: TEST FAILED: ObjectReference.invokeMethod(): caught unexpected com.sun.jdi.InvocationException: Exception occurred in target VM
      [2016-03-29T04:16:22.17] # ERROR: when attempted to invoke the method "longMeth (J)J"
      [2016-03-29T04:16:22.17] # ERROR: got from reference type "class nsk.jdi.ObjectReference.invokeMethod.invokemethod008tDummySuperClass (loaded by instance of jdk.internal.loader.ClassLoaders$AppClassLoader(id=202))"
      [2016-03-29T04:16:22.17] # ERROR: with the arguments: [9223372036854775807]"
      [2016-03-29T04:16:22.17] # ERROR: using the debuggee object reference "instance of nsk.jdi.ObjectReference.invokeMethod.invokemethod008tDummyClass(id=204)"
      [2016-03-29T04:16:22.18] # Test level exit status: 97


      nsk/jdi/VoidValue/toString/tostring001 fails in hs nightly with the following:

      [2016-03-29T04:18:06.95] # ERROR: debugger FAILURE > Unexpected com.sun.jdi.InvocationException: Exception occurred in target VM when invoking debuggee's method: MvY
      [2016-03-29T04:18:06.97] # Test level exit status: 97

        Issue Links

          Activity

          Hide
          sspitsyn Serguei Spitsyn added a comment - - edited
          It is possible the JDK-8152686 has the same root cause.
          It has to be proven first and then this bug can be closed as dup of the JDK-8152686.

          At this point, I was not able to reproduce this yet in 100 runs.
          Show
          sspitsyn Serguei Spitsyn added a comment - - edited It is possible the JDK-8152686 has the same root cause. It has to be proven first and then this bug can be closed as dup of the JDK-8152686 . At this point, I was not able to reproduce this yet in 100 runs.
          Hide
          sspitsyn Serguei Spitsyn added a comment - - edited
          I closed this bug as a dup of: https://bugs.openjdk.java.net/browse/JDK-8152586
          The symptom is same as in the bug JDK-8152586.
          Show
          sspitsyn Serguei Spitsyn added a comment - - edited I closed this bug as a dup of: https://bugs.openjdk.java.net/browse/JDK-8152586 The symptom is same as in the bug JDK-8152586 .
          Hide
          jwilhelm Jesper Wilhelmsson added a comment -
          Removed integration_blocker label since closed as duplicate. (Duplicates are not blockers.)
          Show
          jwilhelm Jesper Wilhelmsson added a comment - Removed integration_blocker label since closed as duplicate. (Duplicates are not blockers.)

            People

            • Assignee:
              asapre Amit Sapre
              Reporter:
              rprotacio Rachel Protacio (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: