-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8361529: GenShen: Fix bad assert in swap card tables #26228
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
8361529: GenShen: Fix bad assert in swap card tables #26228
Conversation
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
@earthling-amzn 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 1 new commit pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
This backport pull request has now been updated with issue from the original commit. |
@earthling-amzn The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
If the priority of this bug (I see that the issue type is Task, which seems wrong) is correct, then this doesn't meet the criteria for backporting to JDK 25 during RDP1. See JEP 3. |
Yes, the ticket should have been marked a bug, thank you for fixing that. This change to the assert really should have been made with the same commit where we fixed an issue it uncovered (#26246). We can leave the assertion change out, but it's also low risk (only affects Shenandoah debug builds). |
If this is objectively a P3, then you could raise the priority. Otherwise, maybe consider backporting it to jdk25u? |
Since, as you pointed out, this is a follow-on to the other fix, raising the priority seems OK to me. |
There are test failures, I assume they are fixed by #26246? Integrate that one first and confirm there are no failures then? (I think you can technically update the |
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.
Looks fine for JDK 25.
/integrate |
Going to push as commit 20fc8f7.
Your commit was automatically rebased without conflicts. |
@earthling-amzn Pushed as commit 20fc8f7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Clean backport. Fixes bad pointer in assert.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26228/head:pull/26228
$ git checkout pull/26228
Update a local copy of the PR:
$ git checkout pull/26228
$ git pull https://git.openjdk.org/jdk.git pull/26228/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26228
View PR using the GUI difftool:
$ git pr show -t 26228
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26228.diff
Using Webrev
Link to Webrev Comment