-
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
8327486: java/util/Properties/PropertiesStoreTest.java fails "Text 'xxx' could not be parsed at index 20" after 8174269 #18155
Conversation
…xx' could not be parsed at index 20" after 8174269 The DATE_FORMAT_PATTERN is set to "EEE MMM dd HH:mm:ss zzz uuuu", is the time format of US. So, creates a formatter should using Locale.US, rather than Locale.ROOT, i.e empty. Signed-off-by: sendaoYan <yansendao.ysd@alibaba-inc.com>
👋 Welcome back syan! A progress list of the required criteria for merging this PR into |
@sendaoYan The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
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. Although setting Locale.US
to acquire the formatter is correct, the reasoning is not. The real reason is that Date.toString()
uses Locale.US
explicitly for printing the time zone
sb.append(zi.getDisplayName(date.isDaylightTime(), TimeZone.SHORT, Locale.US)); // zzz |
Also, update the copyright year to 2024.
Done. |
GHA: riscv cross compile fail. It's unrelated to this PR. |
Signed-off-by: sendaoYan <yansendao.ysd@alibaba-inc.com>
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
@sendaoYan 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 40 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@naotoj) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@sendaoYan |
/integrate |
@sendaoYan |
/sponsor |
Going to push as commit e21da4c.
Your commit was automatically rebased without conflicts. |
@DamonFool @sendaoYan Pushed as commit e21da4c. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@naotoj Thanks for the review. |
@DamonFool Thanks. |
Date.toString() uses Locale.US explicitly for printing the time zone, so replace Locale.ROOT to Locale.US in this testcase for fix the test failure.
This testcase fixed has been verified.
Only change the testcase, risk is low.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18155/head:pull/18155
$ git checkout pull/18155
Update a local copy of the PR:
$ git checkout pull/18155
$ git pull https://git.openjdk.org/jdk.git pull/18155/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18155
View PR using the GUI difftool:
$ git pr show -t 18155
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18155.diff
Webrev
Link to Webrev Comment