clockworklabs / clockworklabs/SpacetimeDB
CI flake: couldn't find remote ref
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 merge-queue run succeeded in a later merge-queue run without a new PR head commit.
Tests:
Smoketests (Windows)
Error:
fatal: couldn't find remote ref refs/heads/gh-readonly-queue/master/pr-5243-2161148e8af4050c74d3419c7a71d62c3131f88f
The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/27477572490/job/81221727895 (Smoketests (Windows), attempt merge queue run 27477572490 -> merge queue run 27478430750)
Context:
- Merge queue PR: #5243
- PR head SHA: 2161148e8af4050c74d3419c7a71d62c3131f88f
- Later successful run: https://github.com/clockworklabs/SpacetimeDB/actions/runs/27478430750
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 run for “Smoketests (Windows)” and compare it with the later successful merge-queue run, focusing on the missing gh-readonly-queue remote ref. Trace where that ref is fetched or used in the job; done means identifying and fixing the intermittent failure, with the Windows smoketest completing reliably in merge-queue runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100