-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8327238: Remove MetadataAllocationFailALot* develop flags #18133
8327238: Remove MetadataAllocationFailALot* develop flags #18133
Conversation
Hi all, please review this trivial removal of the `MetadataFailAlot` flags; one of them, `MetadataAllocationFailALotInterval` is unused anyway, and the other `MetadataAllocationFailALot` only prevents the attempt to retry metadata allocation in the VM operation. This functionality does not seem to stress metadata allocation failure at all, just execution of the metadata VM operation, so I decided to just drop the second flag as well. I considered keeping it maybe as `MetadataAllocationFailRetry` or something, but decided against it since it does not seem interesting to test. However I can at reviewer's request do that. Testing: local compilation, gha, grepping hotspot tests/hotspot sources Thanks, Thomas
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
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.
@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 21 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 @lgxbslgx @albertnetymk for your reviews |
Going to push as commit 784f11c.
Your commit was automatically rebased without conflicts. |
Hi all,
please review this trivial removal of the
MetadataFailAlot
flags; one of them,MetadataAllocationFailALotInterval
is unused anyway, and the otherMetadataAllocationFailALot
only prevents the attempt to retry metadata allocation in the VM operation.This functionality does not seem to stress metadata allocation failure at all, just execution of the metadata VM operation, so I decided to just drop the second flag as well.
I considered keeping it maybe as
MetadataAllocationFailRetry
or something, but decided against it since it does not seem interesting to test. However I can at reviewer's request do that.Testing: local compilation, gha, grepping hotspot tests/hotspot sources
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18133/head:pull/18133
$ git checkout pull/18133
Update a local copy of the PR:
$ git checkout pull/18133
$ git pull https://git.openjdk.org/jdk.git pull/18133/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18133
View PR using the GUI difftool:
$ git pr show -t 18133
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18133.diff
Webrev
Link to Webrev Comment