You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disable cache-on-failure (save-always: false on julia-actions/cache@v3) (#119)
## Summary
`julia-actions/cache@v3` (introduced via #118) saves caches **on job
failure** by default, where v2 only saved on success. The escape hatch
documented in the v3 release notes is `save-always: false`. This PR sets
that on every `julia-actions/cache@v3` invocation in the reusable
workflows here.
The new v3 default is reasonable for the common case (test-failure
retries reuse the expensive depot install). But when the failure is in
the *setup* itself — a half-installed depot, an aborted `Pkg` precompile
— the broken state is cached, the restore-key prefix matches subsequent
runs, and every retry restores the broken state and fails identically.
Reruns alone can't recover; the cache has to be manually evicted or
expire.
This was hit on
[`ITensor/ITensorNetworks.jl#373`](ITensor/ITensorNetworks.jl#373):
a fresh Windows run failed in `Pkg.test` precompilation (`ChainRulesCore
is required but does not seem to be installed`), the broken state was
cached, and two reruns reproduced the failure verbatim by restoring from
that cache.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments