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
8267845: Add @requires to avoid running G1 large pages test with wrong page size #4226
Conversation
|
@kstefanj This change now passes all automated pre-integration checks. 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 17 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.
|
/integrate |
Thanks for the reviews @tschatzl and @kimbarrett |
@kstefanj Since your change was applied there have been 37 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit ce44cd6. |
Please review this small test-fix.
Summary
These two tests try to verify that large pages are used correctly for the heap and the G1 internal data structures. The tests start separate processes that are run with specific arguments to know the expected outcome. The sub-processes don't inherit any parameters passed to the test. This is good, but if the parameter
LargePageSizeInBytes
is passed to the test, the driver process will run with this flag and pick up a different large page size than test-processes. This won't work since the driver will use its found large page size to verify the output from the test.The simple fix is to simply not run this test if this flag is specified. For the test to work with this flag, more work has to be done to analyze how different page sizes will affect the test and for now I think this is the best approach.
Testing
Manual verification the the tests won't run if
LargePageSizeInBytes
is set.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4226/head:pull/4226
$ git checkout pull/4226
Update a local copy of the PR:
$ git checkout pull/4226
$ git pull https://git.openjdk.java.net/jdk pull/4226/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4226
View PR using the GUI difftool:
$ git pr show -t 4226
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4226.diff