Repository navigation
ci: keep Windows opam cache resident (base-only dune saves, trim, stable key) - #232
Merged
Merged
Conversation
…rimmed dune cache, stable OCaml env key
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
1 participant
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.
Repo Actions cache was at 12.9GB (>10GB cap): per-PR dune caches (~0.8-1GB each) evicted the Windows OCaml switch, so Windows native-tests fell back to ~20-25 min cold opam setup.
actions/cache/restore); only push runs trim (dune cache trim --size=400MB) and save.