-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8342988: GHA: Build JTReg in single step #21692
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 shade! A progress list of the required criteria for merging this PR into |
|
@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 36 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 |
Webrevs
|
|
Can we trust the cache that much? I mean, up to now it's only been a performance hack, now it will become a necessary part of the pipeline. |
Yeah, I guess that's the risk. I can redo this to use the same upload/download-artifact we use to transfer bundles between build and test jobs. Probably next week. |
Actually, as I read "Caching dependencies to speed up workflows", this is not as high of the risk: "GitHub will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. Once a repository has reached its maximum cache storage, the cache eviction policy will create space by deleting the oldest caches in the repository." I don't think we are anywhere close to 10GB limit for a single PR. I guess we can have some thrashing when there are multiple PRs in flight. Using artifacts would likely be more bullet-proof. |
|
Reworked for artifacts. My limited tests passed. Let's see if full GHA test passes with it. |
Passed. @magicus, take a look again? |
|
Overall this looks very nice; thanks! I left a few qestions, just. |
magicus
left a comment
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.
Ship it!
|
Aye. /integrate |
|
Going to push as commit 88dc655.
Your commit was automatically rebased without conflicts. |
It is visible in current GHA runs that building jtreg sometimes break on dependencies checkout, for example:
I suppose this is a side-effect of pulling lots of dependencies all at once. Building jtreg on every platform exposes us to these issues more often. Additionally, we had problems with building jtreg on various platforms.
We do not have to build jtreg for every platform. We can just have a job step that does it once, and stores it in the cache for all dependent jobs to use. It would also save some build time across various jobs.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21692/head:pull/21692$ git checkout pull/21692Update a local copy of the PR:
$ git checkout pull/21692$ git pull https://git.openjdk.org/jdk.git pull/21692/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21692View PR using the GUI difftool:
$ git pr show -t 21692Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21692.diff
Webrev
Link to Webrev Comment