Closed
Conversation
Collaborator
|
Review requested:
|
Contributor
|
Its duplicate of #61474 |
Member
|
Thanks for opening this PR, sadly this is a dupe of #61474 |
Member
|
Based on mozilla/sccache#2566, I don't think this update will fix the cache thrashing issue |
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.
Summary
Updates
sccacheversion tov0.13.0in GitHub Actions workflows.This update addresses the recent GitHub Actions Cache rate limit changes (200 uploads/minute) that were causing cache thrashing and 429 errors as reported in #61436.
The
v0.13.0release of sccache (released Jan 13, 2026) likely contains the necessary adjustments for the rate limit policy enforced on Jan 16, 2026.References:
Checklist