JDK-8296100 : java/util/TimeZone/CustomTzIDCheckDST.java failed with "Got unexpected timezone information"
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 20
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2022-10-30
  • Updated: 2022-11-10
Related Reports
Relates :  
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:(6/243)----------
command: main CustomTzIDCheckDST
reason: User specified action: run main/othervm CustomTzIDCheckDST 
started: Sat Oct 29 22:00:27 GMT 2022
Mode: othervm [/othervm specified]
finished: Sat Oct 29 22:00:28 GMT 2022
elapsed time (seconds): 1.353
----------configuration:(0/0)----------
----------System.out:(11/1864)----------
Command line: [/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-20+22-1573/macosx-x64-debug.jdk/jdk-20/fastdebug/bin/java -cp /System/Volumes/Data/mesos/work_dir/slaves/0c72054a-24ab-4dbb-944f-97f9341a1b96-S99463/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/3818003d-6277-4bc4-93aa-93307cb373f7/runs/c3bdf78c-9075-47ef-bfe1-b663b05c4310/testoutput/test-support/jtreg_open_test_jdk_jdk_util/classes/0/java/util/TimeZone/CustomTzIDCheckDST.d:/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-20+22-1573/src.full/open/test/jdk/java/util/TimeZone:/System/Volumes/Data/mesos/work_dir/slaves/0c72054a-24ab-4dbb-944f-97f9341a1b96-S99463/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/3818003d-6277-4bc4-93aa-93307cb373f7/runs/c3bdf78c-9075-47ef-bfe1-b663b05c4310/testoutput/test-support/jtreg_open_test_jdk_jdk_util/classes/0/test/lib:/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-20+22-1573/src.full/open/test/lib:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/7/1/bundles/jtreg-7+1.zip/jtreg/lib/jtreg.jar CustomTzIDCheckDST runTZTest ]
[2022-10-29T22:00:27.530986Z] Gathering output for process 27806
[2022-10-29T22:00:28.221813Z] Waiting for completion for process 27806
[2022-10-29T22:00:28.222037Z] Waiting for completion finished for process 27806
Output and diagnostic info for process 27806 was saved into 'pid-27806-output.log'
[2022-10-29T22:00:28.252466Z] Waiting for completion for process 27806
[2022-10-29T22:00:28.252720Z] Waiting for completion finished for process 27806
[2022-10-29T22:00:28.252927Z] Waiting for completion for process 27806
[2022-10-29T22:00:28.253089Z] Waiting for completion finished for process 27806
[2022-10-29T22:00:28.301174Z] Waiting for completion for process 27806
[2022-10-29T22:00:28.301376Z] Waiting for completion finished for process 27806
----------System.err:(19/1095)----------
 stdout: [];
 stderr: [Exception in thread "main" java.lang.RuntimeException: Got unexpected timezone information: Sun Oct 30 00:00:27 GMT+02: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], exit value is: [1]
	at jdk.test.lib.process.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:490)
	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:125)
	at java.base/java.lang.Thread.run(Thread.java:1591)

JavaTest Message: Test threw exception: java.lang.RuntimeException: Expected to get exit value of [0], exit value is: [1]
JavaTest Message: shutting down test


This failure mode matches the following closed bug:

JDK-8288369 java/util/TimeZone/CustomTzIDCheckDST.java failed with "RuntimeException: Got unexpected timezone information"

but that bug was closed as a duplicate of another bug that has
since been fixed. I don't want to reopen JDK-8288369 and have
to deal with the muddled history so I've created a new bug.

Comments
Thanks Daniel. I will pass that along. I know Gaurav has been working to replicate this this failure, but has not been successful. I see you're running it on linux_x64 with fastdebug. Are there any other particulars to the test run, or configuration that may affect this test?
10-11-2022

Here's the log file from my jdk-20+21 sighting on linux-x64: $ unzip -l jdk-20+21_linux-x64.8296100.zip Archive: jdk-20+21_linux-x64.8296100.zip Length Date Time Name --------- ---------- ----- ---- 17582 2022-10-29 20:00 jdk-20+21_3/failures.linux-x86_64/CustomTzIDCheckDST.jtr.fastdebug --------- ------- 17582 1 file
10-11-2022

Assigning this to [~tsteele] on behalf of Gaurav Chaudhari.
31-10-2022