Repository navigation
Avoid stalled npm cache uploads on self-hosted runners - #31
Merged
Merged
Conversation
11 of 13 tasks
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
1 participant
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.
Required Tests checks remain in
Post Run actions/setup-node@v7for several minutes after every validation step succeeds (runs 39144314246, 39144321128 and 39144737225). The Mac mini fleet already retains npm's download cache locally; archiving and uploading that shared cache delays PR merges.Disable setup-node's package-manager cache in all six Node setup steps. Keep Node provisioning,
npm ci, and the persistent local npm cache. Document the setting in the runner prerequisites. No required validation is removed.Validation: checked all setup-node invocations and
git diff --check; required Tests and Documentation workflows will verify the change on the Mac mini runners.