-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8323717: Introduce test keyword for tests that need external dependencies #17421
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
8323717: Introduce test keyword for tests that need external dependencies #17421
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
Any takers? Maybe the audience should include core-libs too. /label add core-libs |
@shipilev |
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.
Seems quite reasonable.
@shipilev 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 236 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! I shall wait for more reviewers, in case someone has an issue with |
Is there any place to document the new keyword or its usage; it does not seem very discoverable just existing in the TEST.ROOT and some tests. |
I don't think there is a place to describe keywords, except in the relevant |
@lmesnik, you good with the keyword name? |
Yes, I'm fine. |
Awesome, thanks. /integrate |
Going to push as commit 12b89cd.
Your commit was automatically rebased without conflicts. |
Some jtreg tests require resolvable external dependencies. This resolution is delegated to JIB, which is not used in vanilla OpenJDK testing. It would be convenient to add a keyword that marks tests that require these external dependencies, so that we could exclude those tests from runs. This would allow us to: a) run all tests in hotspot:tier4, which now excludes
applications/
specifically; b) make all tests runs (#17422) cleaner on many environments.I provisionally call this flag
external-dep
, but I am open for other suggestions.Note that some tests that pull
@Artifact
-s provide special paths that do limited testing anyway. However, there are tests which cannot run without external dependencies at all. These include at leastapplications/jcstress
andapplications/scimark
tests.Ironically, I cannot run the jcstress test generator because the dependencies are lacking here. I regenerated those test using a self-built jcstress 0.16 bundle.
Additional testing:
make test TEST=applications/
failsJTREG_KEYWORDS=\!external-dep make test TEST=applications/
passes, skipping most of the testsProgress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17421/head:pull/17421
$ git checkout pull/17421
Update a local copy of the PR:
$ git checkout pull/17421
$ git pull https://git.openjdk.org/jdk.git pull/17421/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17421
View PR using the GUI difftool:
$ git pr show -t 17421
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17421.diff
Webrev
Link to Webrev Comment