On Fri, 26 Aug 2022 07:26:46 GMT, Ichiroh Takiguchi <itakigu...@openjdk.org> wrote:
> After `test/jdk/java/util/TimeZone/CustomTzIDCheckDST.java` testcase was > integrated, it failed on the AIX platform. > > Error output > > STDERR: > stdout: []; > stderr: [Exception in thread "main" java.lang.RuntimeException: Got > unexpected timezone information: Thu Aug 25 09:29:10 CEST 2022 > at CustomTzIDCheckDST.runTZTest(CustomTzIDCheckDST.java:71) > at CustomTzIDCheckDST.main(CustomTzIDCheckDST.java:50) > ] > > > By my investigation, `TZ=MEZ-1MESZ,M3.5.0,M10.5.0` timezone was changed to > `Europe/Berlin` timezone on AIX platform. > It seems this situation is happened because older AIX did not support > `MEZ-1MESZ,M3.5.0,M10.5.0` timezone by TZ environment variable. > https://www.ibm.com/support/pages/managing-time-zone-variable-posix > AIX special code was implemented into > `src/java.base/unix/native/libjava/TimeZone_md.c`. > Current AIX supports `TZ=EST5EDT,M3.2.0/2:00:00,M11.1.0/2:00:00` style. > I think implementation change is required. > > Some pre-submit tests are failed, but I think these are not related this > change since modified parts are just for AIX platform. src/java.base/unix/native/libjava/TimeZone_md.c line 589: > 587: // But Hotspot does not support XPG_SUS_ENV=ON. > 588: // Ignore daylight saving settings to calculate current time > difference > 589: localtm.tm_isdst = 0; Is it OK to reset it always? Could this defy the original purpose of the fix to https://bugs.openjdk.org/browse/JDK-8285838? ------------- PR: https://git.openjdk.org/jdk/pull/10036
