-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8279662: serviceability/sa/ClhsdbScanOops.java can fail do to unexpected GC #7295
Conversation
👋 Welcome back cjplummer! A progress list of the required criteria for merging this PR into |
@plummercj The following label 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 list. If you would like to change these labels, use the /label pull request command. |
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 reasonable to me.
There is minor duplication but it is okay as there is no good way to get rid of it.
Thanks,
Serguei
@plummercj 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 221 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 |
I considered a loop or common method, but it seemed not to be worth it and likely less readable. |
Agreed. |
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.
For the scanoops for a type, it seems like a reasonable assumption that there will be a String in the old gen!
Actually it's not, and that's why I check the Eden gen. If a GC is not triggered, the old gen will be empty. It not actually guaranteed that a String will be in the Eden gen either, but at least at the moment that appears to be the case whether or not a GC is triggered. |
Yes sorry, should have said it's a good bet to find a String when only checking one generation. Carry on... |
/integrate |
Going to push as commit fe0118f.
Your commit was automatically rebased without conflicts. |
@plummercj Pushed as commit fe0118f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The test is failing to find certain types in the scanoops output when run with -Xcomp. This is happening in the loom repo. The reason it is happening there is because loom introduced a full GC during codecache sweeping. The test only runs scanoops on the eden gen, and the full GC is causing objects of certain expected types to no longer be present in the eden gen. The fix is to also check the old gen.
The logic of the test had to be reworked a bit to accomplish checking the output of two scanoops commands together. It was relying on the ClhsdbLauncher class to check the output for expected strings, but in this case we need to accumulate the output of the two scanoops commands and check the combined output for the expected strings, so now the checking is done directly by the test and not by ClhsdbLauncher.
I'm choosing to fix this in the jdk repo rather than the loom repo since it is a latent bug that theoretically could occur even without the loom changes, and also to help reduce the amount of changes to be reviewed when loom is integrated into jdk.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7295/head:pull/7295
$ git checkout pull/7295
Update a local copy of the PR:
$ git checkout pull/7295
$ git pull https://git.openjdk.java.net/jdk pull/7295/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7295
View PR using the GUI difftool:
$ git pr show -t 7295
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7295.diff