CI: Inefficent caching of rust builds
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
I've looked at a few of the latest (successful) runs of the ci.yml workflow and the swatinem/rust-cache steps show that no cache was found. Additionally, clippy jobs are not cached at all.
I think the that actions is not very good at restoring from branches that are close to a cache hit and we can do better with a custom action; in this repo's .github/actions directory or in a different repo in this github organization.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the cache steps and clippy jobs in the ci.yml workflow, then compare recent successful runs to understand the cache misses. Inspect .github/actions for existing custom-action conventions before deciding where the caching change belongs. Done means Rust and clippy builds consistently restore useful caches in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100