JDK-8223388 : TestZoneInfo310.java fails post tzdata2018i integration
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.time
  • Priority: P4
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • OS: generic
  • CPU: generic
  • Submitted: 2019-05-06
  • Updated: 2024-01-18
  • Resolved: 2023-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Duplicate :  
JDK-8212970 - TZ database in "vanguard" format support
Relates :  
JDK-8215982 - (tz) Upgrade Timezone Data to tzdata2018i
Relates :  
JDK-8324065 - Daylight saving information for `Africa/Casablanca` are incorrect
Description
test/jdk/sun/util/calendar/zi/TestZoneInfo310.java fails with below error post integration of tzdata2018i:

Africa/Casablanca : Africa/Casablanca
    offset=0,dstSavings=0,useDaylight=false,transitions=95,offsets=3,checksum=254320564,gmtChanged=false
[NG]offset=0,dstSavings=3600000,useDaylight=false,transitions=95,offsets=3,checksum=254320564,gmtChanged=false
    -------------
Exception in thread "main" java.lang.RuntimeException:   FAILED:  Africa/Casablanca
	at TestZoneInfo310.main(TestZoneInfo310.java:175)
Comments
Year 2037 issue will be resolved in JDK-8324065
18-01-2024
There are two reasons that trigger failures in the test. - Negative DST - javazic's last rule assumes year 2037 (for Iran/Tehran case) These issues need to be resolved in the javazic.
22-07-2019