-
Notifications
You must be signed in to change notification settings - Fork 6k
8349200: [JMH] time.format.ZonedDateTimeFormatterBenchmark fails #23414
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
Conversation
👋 Welcome back syan! A progress list of the required criteria for merging this PR into |
@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 20 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 |
@sendaoYan To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
/label add core-libs |
/label add i18n |
@sendaoYan |
@sendaoYan |
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.
Switch to universal time for the time-zone to generalize the benchmark looks good to me.
The benchmark was provided with the fix to https://bugs.openjdk.org/browse/JDK-8304976, and most likely the failure was due to the removal of COMPAT locale provider. Would you double check the benchmark is relevant with your fix? Since UTC is a special time zone, so I just wanted to double check. If we need more practical short name, "PST" might not be a bad choice |
Yes. git bisect result shows that the failure was due to PR "8174269: Remove COMPAT locale data provider from JDK" And, use jdk22, the difference between '-Djava.locale.providers=COMPAT' and '-Djava.locale.providers=CLDR' also convinced that.
|
I think use "Pacific Standard Time - PST" is a more practical chioce. The PR has been updated. |
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. Thanks for the update
Thanks all for the reviews. /integrate |
Going to push as commit a51e669.
Your commit was automatically rebased without conflicts. |
@sendaoYan Pushed as commit a51e669. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi all,
The JMH test "org.openjdk.bench.java.time.format.ZonedDateTimeFormatterBenchmark.parse" fails "java.time.format.DateTimeParseException: Text '2015:03:10:12:13:ECT' could not be parsed at index 17".
The
ECT
standard for "America/Guayaquil" - "Ecuador Time", and since jdk23 theECT
TimeZone.SHORT doesn't support anymore. Below code snippet shows the difference between jdk22 and jdk23:This PR use
Z
TimeZone.SHORT instead ofECT
will make this test more generic. Change has been verified locally, test-fix only, no risk.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23414/head:pull/23414
$ git checkout pull/23414
Update a local copy of the PR:
$ git checkout pull/23414
$ git pull https://git.openjdk.org/jdk.git pull/23414/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23414
View PR using the GUI difftool:
$ git pr show -t 23414
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23414.diff
Using Webrev
Link to Webrev Comment