oxidecomputer / oxidecomputer/omicron
CI flake: rust-cache timeout
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
https://github.com/oxidecomputer/omicron/actions/runs/5871331819/job/15920417547 failed on the rust-cache step:
...
Received 761198491 of 765392795 (99.5%), 7.4 MBs/sec
Received 761198491 of 765392795 (99.5%), 7.3 MBs/sec
Received 761198491 of 765392795 (99.5%), 7.3 MBs/sec
Received 761198491 of 765392795 (99.5%), 7.2 MBs/sec
Received 761198491 of 765392795 (99.5%), 7.2 MBs/sec
Warning: Failed to restore: The operation cannot be completed in timeout.
No cache found.
Error: The operation was canceled.
This appears to be a fault upstream of the rust-cache action itself; https://github.com/Swatinem/rust-cache/issues/72 has discussions about adding timeouts/retries, but it doesn't look like anything has landed yet.
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 with the linked GitHub Actions run and inspect the rust-cache step, then read the referenced upstream rust-cache issue. No repository file, test, or concrete completion criterion is named, so first determine whether a local CI change is possible or whether the upstream timeout/retry work must land.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100