clockworklabs / clockworklabs/SpacetimeDB
CI flake: sccache failed to start: `cache storage failed to read: Unexpected (temporary) at read => send http request`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
Smoketests (Linux)
Error:
error: process didn't exit successfully: sccache /home/runner/.rustup/toolchains/1.93.0-x86_64-unknown-linux-gnu/bin/rustc -vV (exit status: 2)
--- stderr
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/29417989091/job/87398331602 (Smoketests (Linux), attempt 2 -> 3)
Timeout detection:
- none
Context:
- none
Contributor guide
No contributing guide indexed for this repository
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 failed Smoketests (Linux) GitHub Actions run and the reported sccache invocation for rustc. Compare the failed attempt with its successful rerun and inspect the repository's CI configuration for the cache setup. Done means the intermittent cache-start failure is understood and a concrete, verified CI fix or mitigation is identified.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100