Repository navigation
ci: pilot kache build cache on the Rust test job (WI-1169) - #169
Closed
thedancingdeveloper wants to merge 1 commit into
Closed
thedancingdeveloper wants to merge 1 commit into
thedancingdeveloper wants to merge 1 commit into
Conversation
Add kunobi-ninja/kache-action, pinned to the v1 tag commit, to the self-hosted rust job only. The store is node-local; GitHub Actions cache and PR comments stay off. WI-1169.
Collaborator
Author
|
Shelving kache (WI-1169): cold run 31m08s vs 14–28m baseline, 14.5% hit rate; results on WI-1169. |
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.
Summary
Pilot of kache as a Rust build cache, on the self-hosted
rustjob in.github/workflows/ci.ymlonly. No other job changes, no remote store, no new infrastructure.kunobi-ninja/kache-actionis pinned toad7317540dcdd71c904f7a60a87b620a0c0e67ed, the commit the annotatedv1tag points at (2026-09-25). Inputs:node-cache: truewithcache-dir: /var/cache/kache/rustnzb— persistent local store on the self-hosted runner, not the GitHub Actions cache.github-cache: false— self-hosted runners keep the store on disk.pr-comment: false,job-summary: true.Fork PRs
The action's own write policy is read-only for pull requests, forks, tags,
workflow_dispatchandpull_request_target: it uploads only from pushes to protected branches (README, "How it works" / S3 post step). Withgithub-cache: falsethere is no Actions-cache save at all.node-cacheadditionally rejects fork PRs as defense in depth, so a fork PR cannot seed/var/cache/kache/rustnzb.Measurement plan
Do not merge yet. Compare this PR's
rustjob against recentmainruns of the same job over 1–2 weeks of normal pushes once (if) it lands:rustjobThe first run is a cold cache and should be slower, not faster. Judge the pilot on the second and later runs.
Vogt WI-1169.