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

java/time/test/java/time/TestClock_System.java failed intermittently

    Details

    • Subcomponent:
    • Resolved In Build:
      b105
    • CPU:
      generic
    • OS:
      windows
    • Verification:
      Not verified

      Description

      This was seen once in jdk9 dev nightly b93_2015-11-14-1602_3833.

      Please see the following test output:
      ----------System.out:(77/4472)----------
      [TestNG] Running:
        java/time/test/java/time/TestClock_System.java


      systemUTC #1 : 2015-11-15T04:25:44.564Z - seconds: 1447561544, nanos: 564000000
      systemUTC #2 : 2015-11-15T04:25:44.564Z - seconds: 1447561544, nanos: 564000000
      highestResolutionUTC #1 : 2015-11-15T04:25:44.564023400Z - seconds: 1447561544, nanos: 564023400
      highestResolutionUTC #2 : 2015-11-15T04:25:44.564023400Z - seconds: 1447561544, nanos: 564023400

      systemUTC : 2015-11-15T04:25:44.565Z - seconds: 1447561544, nanos: 565000000
      highestResolutionUTC : 2015-11-15T04:25:44.565Z - seconds: 1447561544, nanos: 565000000

      Number of time stamps which had better than millisecond precision: 0/1000

      systemUTC : 2015-11-15T04:25:44.565Z - seconds: 1447561544, nanos: 565000000
      highestResolutionUTC : 2015-11-15T04:25:44.565Z - seconds: 1447561544, nanos: 565000000
      test test.java.time.TestClock_System.test_ClockResolution(): failure
      java.lang.RuntimeException: Micro second preccision not reached
      at test.java.time.TestClock_System.test_ClockResolution(TestClock_System.java:203)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:520)
      at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
      at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
      at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
      at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
      at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
      at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
      at org.testng.TestRunner.privateRun(TestRunner.java:767)
      at org.testng.TestRunner.run(TestRunner.java:617)
      at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
      at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
      at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
      at org.testng.SuiteRunner.run(SuiteRunner.java:240)
      at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
      at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
      at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
      at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
      at org.testng.TestNG.run(TestNG.java:1057)
      at com.sun.javatest.regtest.TestNGAction$TestNGRunner.main(TestNGAction.java:163)
      at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:520)
      at com.sun.javatest.regtest.agent.MainActionHelper$SameVMRunnable.run(MainActionHelper.java:218)
      at java.lang.Thread.run(Thread.java:747)
      *** Testing limits ***
      Validating adjustment: 4294967295566953100
      Validating adjustment: -4294967294431093800
      Validating adjustment: 1024568906200
      Validating adjustment: 1024568906200
      Validating adjustment: 1024568906200
      Validating adjustment: 1024568906200
      Validating adjustment: 1447561544568906200
      Validating adjustment: 1447561545568906200
      Validating adjustment: -2147483646431093800
      Validating adjustment: -2147483647431093800
      Validating adjustment: 1024568906200
      Validating adjustment: 1024568906200
      test test.java.time.TestClock_System.test_OffsetLimits(): success
      *** Testing regular cases ***
      Validating adjustment: 568906200
      Validating adjustment: 1024568906200
      Validating adjustment: -1023430117200
      test test.java.time.TestClock_System.test_OffsetRegular(): success
      test test.java.time.TestClock_System.test_systemUTC("Clock.systemUTC()#1", SystemClock[Z]): success
      test test.java.time.TestClock_System.test_systemUTC("Clock.systemUTC()#2", SystemClock[Z]): success
      test test.java.time.TestClock_System.test_systemUTC("Clock.system(ZoneOffset.UTC)#1", SystemClock[Z]): success
      test test.java.time.TestClock_System.test_systemUTC("Clock.system(ZoneOffset.UTC)#2", SystemClock[Z]): success
      test test.java.time.TestClock_System.test_toString(): success
      test test.java.time.TestClock_System.test_withZone_same(): success

      ===============================================
      java/time/test/java/time/TestClock_System.java
      Total tests run: 9, Failures: 1, Skips: 0
      ===============================================

      ----------System.err:(12/649)----------
      Something is strange: no microsecond precision with highestResolutionUTC?
      java.lang.Exception: failures: 1
      at com.sun.javatest.regtest.TestNGAction$TestNGRunner.main(TestNGAction.java:166)
      at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:520)
      at com.sun.javatest.regtest.agent.MainActionHelper$SameVMRunnable.run(MainActionHelper.java:218)
      at java.lang.Thread.run(Thread.java:747)

        Activity

        Hide
        rriggs Roger Riggs added a comment -
        The test would be more robust if it looked for 1000 different values from the clock; the current cpu intensive loop may run pretty fast.
        Show
        rriggs Roger Riggs added a comment - The test would be more robust if it looked for 1000 different values from the clock; the current cpu intensive loop may run pretty fast.
        Hide
        hgupdate HG Updates added a comment -
        URL: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/46d6f4802c9a
        User: rriggs
        Date: 2016-02-01 21:51:37 +0000
        Show
        hgupdate HG Updates added a comment - URL: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/46d6f4802c9a User: rriggs Date: 2016-02-01 21:51:37 +0000
        Hide
        hgupdate HG Updates added a comment -
        URL: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/46d6f4802c9a
        User: lana
        Date: 2016-02-10 21:55:24 +0000
        Show
        hgupdate HG Updates added a comment - URL: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/46d6f4802c9a User: lana Date: 2016-02-10 21:55:24 +0000

          People

          • Assignee:
            rriggs Roger Riggs
            Reporter:
            xiaofeya Felix Yang
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: