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
8282347: AARCH64: Untaken branch in has_negatives stub #659
Conversation
👋 Welcome back bulasevich! A progress list of the required criteria for merging this PR into |
Webrevs
|
e3de458
to
1ff232d
Compare
@bulasevich Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
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.
@bulasevich 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 2 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the 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 (@phohensee, @dsamersoff) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
1ff232d
to
076a289
Compare
@bulasevich Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
same here, please rename PR |
This backport pull request has now been updated with issue from the original commit. |
/integrate |
@bulasevich |
/sponsor |
Going to push as commit 486cffe.
Your commit was automatically rebased without conflicts. |
@dsamersoff @bulasevich Pushed as commit 486cffe. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Same here, please add jdk17u-fix-request retroactively. |
@dsamersoff @bulasevich |
I can't think of any reason that this should qualify for a backport. |
Dear all, My bad, I pushed the fix after PR review and completely forgot the review label mechanism. I am really sorry. Let me ask for jdk17u-fix-request in correspondent JBS records records now. If the request is declined, I am ready to back out the changes. I believe the changes I have pushed ([1] [2] [3]) are trivial, safe and harmless. The reason to bring them is a preparation for a big backport I want to propose - my goal is to bring the StringCoding.countPositives change [4] which has a dependencies:
[1] #657 |
Backport 3efd6aa4c9b6420520709281ab1ca46ba4242c87
A trivial change. Helps JDK-8281146 backport merge issues.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev pull/659/head:pull/659
$ git checkout pull/659
Update a local copy of the PR:
$ git checkout pull/659
$ git pull https://git.openjdk.org/jdk17u-dev pull/659/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 659
View PR using the GUI difftool:
$ git pr show -t 659
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/659.diff