-
Notifications
You must be signed in to change notification settings - Fork 251
6849922: java/awt/Choice/ChoiceKeyEventReaction/ChoiceKeyEventReaction.html fails #351
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
…n.html fails Reviewed-by: kaddepalli, serb
|
👋 Welcome back jdowland! A progress list of the required criteria for merging this PR into |
|
/test tier1 |
|
Test ChoiceKeyEventReaction(.java) passes for me on x86_64 (without also backporting 8214469, which is required to pass on macos) |
|
Oh, you have beaten me by a few hours. I also started doing this backport (https://github.com/realclanger/jdk11u-dev/tree/RealCLanger-backport-1b012e21). 😆 Again, please rename this PR to "Backport <commit-hash>", e.g. 1b012e2 in this case, to make the bots correctly recognize it as a backport. Furthermore, please enable Github Actions here: https://github.com/jmtd/jdk11u-dev/actions because this will give us more confidence. And last but not least, I ran the test on Windows and it passes. |
Oh I'm sorry, I hate it when this happens to me! for 8u, we have/had a convention of labelling issues in JBS with |
|
This backport pull request has now been updated with issue from the original commit. |
|
@jmtd 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 50 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. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
/integrate |
Well, it probably doesn't happen often. When I start, I obviously check whether a PR is already open. The moment you do this (correctly) it get's linked into the issue. The other way to claim a backport for myself would be to create a backport bug with the target release version. However, I usually would do this only for backports where I think the effort and time needed will be considerably high, not for simple apply & build & run tests type of patches. |
|
/sponsor |
|
Going to push as commit 48e5f41.
Your commit was automatically rebased without conflicts. |
|
@RealCLanger @jmtd Pushed as commit 48e5f41. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Backport of JDK-6849922 for jdk11u
Does not apply clean, RFR will be required (ProblemList.txt)
Pre-requisite for JDK-8214469
Test-only changes, awaiting tier1 test results regardless
Note: the test modified by this patch does not pass after applying it, at least on macos -- it does once JDK-8214469 is applied too (that comes next)
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/351/head:pull/351$ git checkout pull/351Update a local copy of the PR:
$ git checkout pull/351$ git pull https://git.openjdk.java.net/jdk11u-dev pull/351/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 351View PR using the GUI difftool:
$ git pr show -t 351Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/351.diff