meta: fix GHA sccache reporting #61639
Open
+6
−0
Conversation
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
Collaborator
|
Review requested:
|
nodejs-github-bot
added
the
meta
aduh95
reviewed
Feb 2, 2026
aduh95
reviewed
Feb 2, 2026
Renegade334
force-pushed
the
gha-sccache-persist-daemon
branch
2 times, most recently
from
433c95e to
57f2a68
Compare
aduh95
approved these changes
Feb 2, 2026
aduh95
added
lts-watch-v20.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
meta: persist sccache daemon until end of build workflows
sccache stores its stats in process memory, and the daemon shuts down after 10 minutes of inactivity by default, which is longer than the test phase of our GHA builds. As a result, our sccache stats reported by GHA at the end of the workflows are all zeroes.
Setting
SCCACHE_IDLE_TIMEOUT=0will cause the sccache daemon to persist for the lifetime of the runner.