-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8347496: Test jdk/jfr/jvm/TestModularImage.java fails after JDK-8347124: No javac #23079
Conversation
👋 Welcome back sgehwolf! A progress list of the required criteria for merging this PR into |
@jerboaa 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 15 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 |
Seems reasonable, as long as the created images don't have other modules it should be fine. |
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. Thanks for fixing!
I agree this was likely always a problem but never observed when run in an agentVM.
/integrate Thanks for the reviews! |
Going to push as commit 3967696.
Your commit was automatically rebased without conflicts. |
Please review this test-only fix. Apparently there are some test configurations out there that run
jdk/jfr/jvm/TestModularImage.java
with limited modules. Specifically--limit-modules java.base,jdk.jfr
. For this particular test that is not sufficient to be able to run the test.TestModularImage.java
uses theToolProvider
API to get a hold ofjavac
as well as forjlink
without them being present the test should be skipped.I've done that by adding those two required modules in the
@modules
tag.Testing:
jdk/jfr/jvm/TestModularImage.java
with test option--limit-modules jdk.jfr,java.base
which now skips the test (instead of failing the test). RunningTestModularImage.java
without the--limit-modules
option and it passes.Thoughts?
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23079/head:pull/23079
$ git checkout pull/23079
Update a local copy of the PR:
$ git checkout pull/23079
$ git pull https://git.openjdk.org/jdk.git pull/23079/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23079
View PR using the GUI difftool:
$ git pr show -t 23079
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23079.diff
Using Webrev
Link to Webrev Comment