clockworklabs / clockworklabs/SpacetimeDB
CI flake: v8 build script fails downloading rusty_v8 archive
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:
Lints
Error:
thread 'main' (20124) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/v8-145.0.0/build.rs:669:3:
assertion failed: status.success()
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/31634062242/job/94239866939 (Lints, attempt 1 -> 2)
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 GitHub Actions Lints run and compare it with the successful rerun. Trace the v8-145.0.0 build.rs download step and determine why the rusty_v8 archive fetch can fail transiently. Done means the Lints job no longer flakes on this download and the relevant CI run succeeds reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100