-
Notifications
You must be signed in to change notification settings - Fork 5.9k
8349358: [JMH] Cannot access class jdk.internal.vm.ContinuationScope #23437
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 syan! A progress list of the required criteria for merging this PR into |
@sendaoYan 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 364 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 |
@sendaoYan To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
/label add core-libs |
@sendaoYan |
Webrevs
|
These are left over from early development, need to decide if they should be removed. |
@sendaoYan This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Should we remove these JMH tests, or just fix the test bug and make tests run normally |
I think that would be best as they are left over from early development. |
…test/micro/org/openjdk/bench/loom/obsolete/OneShot.java test/micro/org/openjdk/bench/loom/obsolete/Oscillation.java
The related test files has been removed in this PR. |
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.
Okay
Thanks @AlanBateman /integrate |
Going to push as commit 5c552a9.
Your commit was automatically rebased without conflicts. |
@sendaoYan Pushed as commit 5c552a9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi all,
Several JMH tests fails "cannot access class jdk.internal.vm.ContinuationScope (in module java.base) because module java.base does not export jdk.internal.vm to unnamed module". This PR add VM option
--add-exports=java.base/jdk.internal.vm=ALL-UNNAMED
to fix the JMH test bug.Change has been verified locally, test-fix only, no risk.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23437/head:pull/23437
$ git checkout pull/23437
Update a local copy of the PR:
$ git checkout pull/23437
$ git pull https://git.openjdk.org/jdk.git pull/23437/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23437
View PR using the GUI difftool:
$ git pr show -t 23437
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23437.diff
Using Webrev
Link to Webrev Comment