filecoin-project / filecoin-project/ref-fvm
CI: cache fuzzer build
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 422
- Forks
- 154
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 12
Description
We spend ~6m building the fuzzer each time we run CI. We should cache something here.
Alternatively, we could just run the fuzzer on master and ditch the per-PR run. Thoughts @Kubuxu?
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
No workflow file or test is named. Start by locating the CI job that builds and runs the fuzzer, then compare caching the build with running it only on master; done means the chosen approach avoids the repeated six-minute build while retaining the intended fuzzer coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100