clockworklabs / clockworklabs/SpacetimeDB
CI flake: Build smoketests (Windows)
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:
Build smoketests (Windows)
Error:
fatal: couldn't find remote ref refs/heads/gh-readonly-queue/master/pr-5739-12812dcf5ae850f17157807095ba58dc710bf960
The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/31755508637/job/94631950160 (Build smoketests (Windows), attempt merge queue run 31755508637 -> merge queue run 31759783120)
Timeout detection:
- none
Context:
- Merge queue PR: #5739
- PR head SHA: 12812dcf5ae850f17157807095ba58dc710bf960
- Later successful run: https://github.com/clockworklabs/SpacetimeDB/actions/runs/31759783120
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 Build smoketests (Windows) job in run 31755508637 and compare it with the later successful run 31759783120. Trace why the merge-queue ref refs/heads/gh-readonly-queue/master/pr-5739-12812dcf5ae850f17157807095ba58dc710bf960 was unavailable, then verify that the Windows smoketest no longer flakes across merge-queue runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100