-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8274340: [BACKOUT] JDK-8271880: Tighten condition for excluding regions from collecting cards with cross-references #5734
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
…ing cards with cross-references" This reverts commit 5a12af7.
|
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
kimbarrett
left a comment
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 good.
|
@tschatzl 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 36 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 |
|
Thanks @albertnetymk @kimbarrett for your reviews. /integrate |
|
Going to push as commit 1dc8fa9.
Your commit was automatically rebased without conflicts. |
Hi all,
please review this backout of JDK-8271880: Tighten condition for excluding regions from collecting cards with cross-references because it causes failures with Kitchensink runs.
As the CR indicates, with proper verification these runs fail fairly quickly after 5-20mins with a remembered set verification failure on the discovered field of some j.l.ref.References instances; without that patch multiple instances are already running for an hour without issue (out of 8h). This is enough evidence for me that the change is responsible, backing it out to keep the CI clean(er) as I do not really have an idea why at this time (another merge issue after splitting up the original change?).
Revert applied cleanly except for the hunk in G1PostEvacuateCollectionSetCleanupTask1::G1PostEvacuateCollectionSetCleanupTask1 line 138: an earlier cleanup moved evacuation failure handling to
G1YoungCollector, causing some merge problems.Testing: gha
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5734/head:pull/5734$ git checkout pull/5734Update a local copy of the PR:
$ git checkout pull/5734$ git pull https://git.openjdk.java.net/jdk pull/5734/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5734View PR using the GUI difftool:
$ git pr show -t 5734Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5734.diff