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
8244508: JFR: FlightRecorderOptions reset date format #2121
Conversation
Hi @pushkarnk, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user pushkarnk" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
This backport pull request has now been updated with issue from the original commit. |
|
Hello Maintainers, Apologies for the ping. I was hoping to get some feedback on this backport request. Thanks! |
Hello Maintainers, Apologies for the ping. I was hoping to get some feedback on this backport request. Please do let me know if there are questions. cc @RealCLanger @GoeLin |
@pushkarnk This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
I'd appreciate feedback on this backport request. Thank you. |
Hi @pushkarnk, I think this backport is appropriate. Can you please run Github Actions verification? (E.g. enable actions here: https://github.com/pushkarnk/jdk11u-dev/actions and then merge the PR with master). Furthermore, I'm wondering why the backport is not marked as clean. What did you have to resolve? Cheers |
/issue JDK-8244508 |
@pushkarnk This issue is referenced in the PR title - it will now be updated. |
Hi @RealCLanger, I've run the checks. The original commit removed an unused import in DCmdConfigure.java which does not exist in jdk11. That's the only conflict I had to resolve. Thanks! |
OK, looks good. I'll run the backport through our tests and will approve when no regressions spotted. |
Hi @RealCLanger, any news on this? |
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.
Oh, sorry and thanks for the ping. I completely forgot about this. Tests are looking good.
|
/approval request |
@pushkarnk |
@pushkarnk, you are supposed to also add some comment as part of the approval request to provide the maintainers some information. That includes some reasoning why you want this backport plus a risk assessment and information about the testing you did. So, please update or re-issue the /approval command with some text. Thx. |
/approve yes |
@GoeLin |
|
@pushkarnk This change now passes all automated pre-integration checks. 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 151 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 (@RealCLanger) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Thanks Chris. I guess this backport request has been approved now. I'll keep this in mind for all future work. |
I requested for this backport because an Ubuntu user reported this bug of JFR not honoring a configured default Locale. Locally, I ran the tier1 tests on Linux x86-64 with |
|
/sponsor |
@RealCLanger The change author (@pushkarnk) must issue an |
/integrate |
@pushkarnk |
Weird that it didn't take your initial /integrate. So be it. /sponsor |
Going to push as commit 7814102.
Your commit was automatically rebased without conflicts. |
@RealCLanger @pushkarnk Pushed as commit 7814102. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hello all,
This backport request is related to JDK-8244508 [1]. When using JFR (
-XX:StartFlightRecording
), the configured default Locale is not honored, with FormatData or TimezoneNames(for example), because the relevant ResourceBundles do not get loaded when an attempt is made to locate and load them during VM startup (i.e when-XX:StartFlightRecording
triggers JFR initialiazation). Though [1] quotes a mailing-list post [2] mentioning this issue was not seen with jdk11 then, the testcase in [1] does fail with 11.0.20 (as well as 11.0.22/master branch) as of today:Testing: Linux x86-64 build, tier1 tests with
release
andfastdebug
builds.[1] https://bugs.openjdk.org/browse/JDK-8244508
[2] https://mail.openjdk.org/pipermail/hotspot-jfr-dev/2020-March/001313.html
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev.git pull/2121/head:pull/2121
$ git checkout pull/2121
Update a local copy of the PR:
$ git checkout pull/2121
$ git pull https://git.openjdk.org/jdk11u-dev.git pull/2121/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2121
View PR using the GUI difftool:
$ git pr show -t 2121
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/2121.diff
Webrev
Link to Webrev Comment