Shared cache keys - #1856
Conversation
Coverage Report for CI Build 33551696687Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage remained the same at 86.64%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Diff mutants should not share the cache key with other stable jobs because of the limited nature of the diff mutants job it can often finish rather quickly and not make a full build if there are no mutants it should not be given the ability to write to the stable-workspace key as it could simply write a nearly empty cache.
698e950 to
584f3ae
Compare
caarloshenriq
left a comment
caarloshenriq
left a comment
There was a problem hiding this comment.
cACK
Lint runs on the same stable toolchain as Test's stable leg (via rust-toolchain.toml default) but its Use cache step wasn't given shared-key: stable-workspace in this PR. Was that intentional, or should it join the unification too?
@caarloshenriq Hmm I thought Lint ran on nightly, no? |
You're right, my mistake |
4 participants
This is an attempt to unify the cache keys between several CI jobs that share the same rust env.
coverage notably is left separate as it apparently cannot use the same cache key as other stable CI jobs.
Coded with GLM 5.3
Pull Request Checklist
Please confirm the following before requesting review:
AI
in the body of this PR.