Repository navigation
ci: stop Azure cache growth from restoreKeys - #3022
Merged
Merged
Conversation
The Azure cache save writes a tar to the agent disk, which is ~95% full after the tests, so the save fails on a cache miss. Assisted-by: ClaudeCode:claude-opus-5-5
Assisted-by: ClaudeCode:claude-opus-5-5
The cache tar is written to /tmp, a 4 GB tmpfs on the Linux agents. restoreKeys carried old interpreters into each new cache, so it grew past that limit. The disk space steps did not help, so remove them. Assisted-by: ClaudeCode:claude-opus-5-5
Contributor
|
thanks for investigating this. |
joerick
approved these changes
Oct 21, 2026
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.
馃 AI text below 馃
The Azure post-job cache step writes the cache tar to
/tmp, which is a 4 GB tmpfs on the Linux agents.restoreKeysseeded each new cache with the old one, so stale interpreters accumulated (20+ old CPython tarballs, ~3.7 GB). On a cache miss, the tar does not fit and the job fails (Wrote only 8192 of 10240 bytes), for example on #3016.This removes
restoreKeysand bumps the key tov2, so each cache holds only the current downloads.