-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8299194: CustomTzIDCheckDST.java may fail at future date #11756
Conversation
👋 Welcome back itakiguchi! A progress list of the required criteria for merging this PR into |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix. Looks good overall. A couple of minor comments/questions.
} else { | ||
runTZTest(); | ||
} | ||
} | ||
|
||
/* TZ code will always be set to "MEZ-1MESZ,M3.5.0,M10.5.0". | ||
/* TZ code will always be set to "MEZ-1MESZ,M3.5.0,M10.5.0/3". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably adding "northern hemisphere" is helpful here.
String tzStr = System.getenv("TZ"); | ||
if (tzStr == null) | ||
throw new RuntimeException("Got unexpected timezone information: TZ is null"); | ||
boolean nor = tzStr.matches(".*,M3\\..*,M10\\..*"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to use RegEx? A simple comparison with CUSTOM_TZ
does not work?
Thanks @naotoj . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@takiguc This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 15 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 5e2de89.
Your commit was automatically rebased without conflicts. |
test/jdk/java/util/TimeZone/CustomTzIDCheckDST.java may fail at future date.
I used following standalone testcase
I tested CheckDST with faketime, then I got following results
I assume
TZ=MEZ-1MESZ
refers Europe/Berlin timezone.In this case,
TZ
environment variable should beMEZ-1MESZ,M3.5.0,M10.5.0/3
(/3
is missing in testcase)CustomTzIDCheckDST should run with daylight saving time.
Add Simulate Southern Hemisphere by
MEZ-1MESZ,M10.5.0,M3.5.0/3
Tested by standalone testcase
Check Europe/Berlin timezone settings
Test results are as follows:
Northern Hemisphere side
Southern Hemisphere side
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11756/head:pull/11756
$ git checkout pull/11756
Update a local copy of the PR:
$ git checkout pull/11756
$ git pull https://git.openjdk.org/jdk pull/11756/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11756
View PR using the GUI difftool:
$ git pr show -t 11756
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11756.diff