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

Safepoint sync time did not increase

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 7, 8, 9
    • Fix Version/s: 11
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b18

      Backports

        Description

        jdk/test/sun/management/HotspotRuntimeMBean/GetSafepointSyncTime.java


        java.lang.RuntimeException: Safepoint sync time did not increase (value1 = 8; value2 = 8)
        at GetSafepointSyncTime.main(GetSafepointSyncTime.java:85)
        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:543)
        at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
        at java.base/java.lang.Thread.run(Thread.java:844)


        We have seen a few issues with clocks recently, not sure if this is related to that. Or it could be that the test expects time to pass between two points in the program even though there is no real guarantee for this to happen. We have seen that in a few other tests. Or there could be a VM bug of course :)

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dholmes David Holmes
                  Reporter:
                  jwilhelm Jesper Wilhelmsson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: