Repository navigation
Conversation
This reverts commit 0a8c5da, which pointed CI at an old mache branch whose jigsaw build pins libnetcdf 4.10.0, conflicting with the 4.10.1 pin in deploy/pins.cfg. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Every CI job that runs ./deploy.py rebuilds JIGSAW, which takes about three minutes. mache 5.2.0 already keeps a content-keyed build cache under .mache_cache/jigsaw, so persist it with actions/cache in the build, docs and GIS workflows. A composite action holds the key, so the three workflows cannot drift apart and miss the cache that main's build workflow saves. The key uses the jigsaw-python submodule commit (which hashFiles cannot see), the Python version and the mache pin. The mache pin is needed because mache's key includes its own build recipe: without it, a primary-key hit on a stale slot would rebuild on every run and never save. The path lists the children of .mache_cache/jigsaw because actions/cache globs without implicit descendants, so an exclusion under a bare directory path would be ignored. This keeps the shared build tools (about 110 MB) out of the cache. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
1 task done
Collaborator
Author
TestingI re-ran CI on this branch after the first run saved the caches. Every job restored its cache and logged
All jobs passed. The GIS job needed a second re-run after Posted by Claude Code on @xylar's behalf. The testing, analysis and wording above are AI-authored; please check them accordingly. |
xylar
added a commit
to E3SM-Project/polaris
that referenced
this pull request
Oct 23, 2026
Every CI job that runs ./deploy.py rebuilds JIGSAW, which takes about three minutes. mache already keeps a content-keyed build cache under .mache_cache/jigsaw, so persist it with actions/cache in the build and docs workflows. A composite action holds the key, so the workflows cannot drift apart and miss the cache that main's build workflow saves. The key uses the jigsaw-python submodule commit (which hashFiles cannot see), the Python version and the mache pin. The mache pin is needed because mache's key includes its own build recipe: without it, a primary-key hit on a stale slot would rebuild on every run and never save. The path lists the children of .mache_cache/jigsaw because actions/cache globs without implicit descendants, so an exclusion under a bare directory path would be ignored. This keeps the shared build tools (about 110 MB) out of the cache. This is the same change as MPAS-Dev/compass#1009. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR caches mache's JIGSAW build in CI, so
./deploy.pyreuses it instead of spending about three of a job's six minutes rebuilding. The build, docs and GIS workflows share one cache key, so pull requests restore the cache thatmainsaves. The key changes with the jigsaw-python submodule, the Python version and the mache pin.This is on top of #1008, which brings in mache 5.2.0 and its JIGSAW cache. Only the last commit is new here, and I will rebase once #1008 merges.
For the reviewer:
.github/actions/, rather than repeated in each workflow the way the pixi cache step is.Checklist
Testingin this PR) any testing that was used to verify the changesPosted by Claude Code on @xylar's behalf. The testing, analysis and wording above are AI-authored; please check them accordingly.