-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8276825: hotspot/runtime/SelectionResolution test errors #6300
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
👋 Welcome back hseigel! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
Hi Harold,
The fix looks good but I'm unclear about the exact circumstances here. Were these tests failing? If so were they excluded somehow? Or were these still passing by accident - which indicates a bigger problem with the test?
Thanks,
David
@hseigel 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 30 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 |
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 to me.
Thanks David and Aleksey for the reviews. The tests passed by accident. The calls to the Clazz constructor happen to succeed because the constructor adds ACC_SUPER to the incoming access. When the access is -1, this results in access being set to 31 because ACC_SUPER equals 32. I changed the Clazz cosntructor java to 'or' the incoming access with ACC_SUPER instead of adding it. This will prevent the test from succeeding in the future if an index of -1 is passsed as the access. Does this latest change look okay? |
So does that mean we check access by AND'ing with a mask ie
So access bits of 31 are the same as 1 from an access check perspective? |
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.
Changes seem fine.
Thanks,
David
Thanks David! /integrate |
Going to push as commit 55b36c6.
Your commit was automatically rebased without conflicts. |
Please review this trivial fix to a few of the hotspot/runtime/SelectionResolution test class files. The fix was tested by running the tests locally and Mach5 tiers 1-3 on Linux, MacOS, and Windows.
Thanks, Harold
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6300/head:pull/6300
$ git checkout pull/6300
Update a local copy of the PR:
$ git checkout pull/6300
$ git pull https://git.openjdk.java.net/jdk pull/6300/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6300
View PR using the GUI difftool:
$ git pr show -t 6300
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6300.diff