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

vmTestbase monitoring tests fail after JSR 166 refresh

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 14
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      svc
    • Resolved In Build:
      b17

      Description

      (Split off from JDK-8231032)

      After JDK-8229442 many of the vmTestbase tests that use locking are failing because the stacktraces have changed, resulting in unexpected or missing stacktrace elements:

      - vmTestbase/nsk/monitoring/ThreadMXBean/ThreadInfo/SynchronizerLockingThreads/SynchronizerLockingThreads*

      Checking: nsk.monitoring.share.thread.SynchronizerLockingThreads@6c0bee43
      Unexpected stack trace elements for: nsk.monitoring.share.thread.SynchronizerLockingThreads$Thread2@5b76c522
         at java.base@14-ea/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3137)

      - vmTestbase/nsk/monitoring/ThreadMXBean/ThreadInfo/Multi/Multi*

      Checking: nsk.monitoring.share.thread.SynchronizerLockingThreads@6d4b092f
      Unexpected stack trace elements for: nsk.monitoring.share.thread.SynchronizerLockingThreads$Thread2@766e069
         at java.base@14-ea/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3137)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              martin Martin Buchholz
              Reporter:
              martin Martin Buchholz
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: