JDK-8288369 : java/util/TimeZone/CustomTzIDCheckDST.java failed with "RuntimeException: Got unexpected timezone information"
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: 20
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: aarch64
  • Submitted: 2022-06-13
  • Updated: 2022-10-30
  • Resolved: 2022-06-14
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Sub Tasks
JDK-8288370 :  
Description
The following test failed in the JDK20 CI:

java/util/TimeZone/CustomTzIDCheckDST.java

Here's a snippet from the log file:

#section:main
----------messages:(4/166)----------
command: main CustomTzIDCheckDST
reason: User specified action: run main/othervm CustomTzIDCheckDST 
Mode: othervm [/othervm specified]
elapsed time (seconds): 0.396
----------configuration:(0/0)----------
----------System.out:(9/1784)----------
Command line: [/opt/mach5/mesos/work_dir/jib-master/install/jdk-20+2-39/linux-aarch64.jdk/jdk-20/bin/java -cp /opt/mach5/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S68412/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/30302b38-4f61-4ee3-9bdb-3da6d24e5b60/runs/d7c4fca9-6b4d-4549-8e57-360b963668ef/testoutput/test-support/jtreg_open_test_jdk_tier1_part2/classes/3/java/util/TimeZone/CustomTzIDCheckDST.d:/opt/mach5/mesos/work_dir/jib-master/install/jdk-20+2-39/src.full/open/test/jdk/java/util/TimeZone:/opt/mach5/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S68412/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/30302b38-4f61-4ee3-9bdb-3da6d24e5b60/runs/d7c4fca9-6b4d-4549-8e57-360b963668ef/testoutput/test-support/jtreg_open_test_jdk_tier1_part2/classes/3/test/lib:/opt/mach5/mesos/work_dir/jib-master/install/jdk-20+2-39/src.full/open/test/lib:/opt/mach5/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/javatest.jar:/opt/mach5/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/jtreg.jar CustomTzIDCheckDST runTZTest ]
[2022-06-13T23:14:15.389879483Z] Gathering output for process 1716148
[2022-06-13T23:14:15.557317512Z] Waiting for completion for process 1716148
[2022-06-13T23:14:15.557509434Z] Waiting for completion finished for process 1716148
Output and diagnostic info for process 1716148 was saved into 'pid-1716148-output.log'
[2022-06-13T23:14:15.562303306Z] Waiting for completion for process 1716148
[2022-06-13T23:14:15.562414826Z] Waiting for completion finished for process 1716148
[2022-06-13T23:14:15.562508507Z] Waiting for completion for process 1716148
[2022-06-13T23:14:15.562574947Z] Waiting for completion finished for process 1716148
----------System.err:(21/1037)----------
 stdout: [];
 stderr: [Exception in thread "main" java.lang.RuntimeException: Got unexpected timezone information: Mon Jun 13 01:14:15 GMT-22:00 2022
	at CustomTzIDCheckDST.runTZTest(CustomTzIDCheckDST.java:71)
	at CustomTzIDCheckDST.main(CustomTzIDCheckDST.java:50)
]
 exitValue = 1

java.lang.RuntimeException: Expected to get exit value of [0]

	at jdk.test.lib.process.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:489)
	at CustomTzIDCheckDST.main(CustomTzIDCheckDST.java:48)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:578)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
	at java.base/java.lang.Thread.run(Thread.java:1596)

JavaTest Message: Test threw exception: java.lang.RuntimeException: Expected to get exit value of [0]

JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Expected to get exit value of [0]
----------rerun:(34/6363)*----------

I'm starting this bug out as a P3 since it is a Tier1 failure, but there's
no obvious correlation to the failing build-ID's changeset.
Comments
Caused by JDK-8285838. The offset calculation appears wrong. The offset calculation needs to check whether the two times refer to the same day, and if not, then adjust by 24 hours.
14-06-2022

The test seems to expect to see GMT+2 but instead gets GMT-22 - which is of course the same time-of-day.
14-06-2022

There is no changeset associated with this issue so it cannot be closed as "Fixed" - really this should have become the REDO issue so I will close it as a duplicate of that. Note the test was never actually ProblemListed.
14-06-2022

The offending test case has now been backed out with JDK-8288378.
14-06-2022