ci: disable caching on Windows tests #9318
Merged
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.
Related Issues
Proposed Changes:
How did you test it?
CI - triggered tests in c33c2dd
CI Runtime Comparison
Non-Windows test times are included for context but are unaffected by the Windows caching configuration.
Although the root cause of the cache slowdown on Windows is still unclear (investigation in #9319), disabling it offers two benefits:
Integration / windows-latest
job (slowest job in tests).Unit / windows-latest
requires about 15s. Skipping this allows integration tests start sooner.Notes for the reviewer
Over time, we should evaluate if it's worth re-enabling cache.