-
Bug
-
Resolution: Fixed
-
P3
-
7, 8, 9
-
b18
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8205212 | 11.0.1 | David Holmes | P3 | Resolved | Fixed | team |
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 :)
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 :)
- backported by
-
JDK-8205212 Safepoint sync time did not increase
-
- Resolved
-
- relates to
-
JDK-5094295 sun/management/HotspotRuntimeMBean/GetTotalSafepointTime fails due to invalid safepoint time
-
- Closed
-