Repository navigation
CI flake: Smoketests (Windows 1/4) #6403
Description
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
Smoketests (Windows 1/4)
Error:
Could not fetch job logs: Command '['gh', 'api', '-X', 'GET', 'repos/clockworklabs/SpacetimeDB/actions/jobs/122501960035/logs']' returned non-zero exit status 1.
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/40591908955/job/122501960035 (Smoketests (Windows 1/4), attempt 1 -> 2)
Timeout detection:
- none
Context:
- none
Activity
clockwork-labs-bot commentedon Oct 27, 2026
Symptoms and root cause
Exact failed job: run
40591908955, job122501960035, attempt 1,Smoketests (Windows 1/4). GitHub's exact check annotation reports the self-hosted runner lost communication with the server. Runnerghr-56b62c17ran 22:13–22:23 UTC on October 27;Install TypeScript SDK dependenciesremainedin_progress, and smoketest execution was still pending. This is runner loss before tests, not a smoketest assertion. Exact-job logs return HTTP 404; host termination, resource starvation, and network interruption remain unproven possibilities. Attempt 2, job122511900262, succeeded on runnerghr-3340d67b, including the Windows smoketests.Duplicate selection
Propose #5799, confirmed OPEN immediately before this report. Its exact-job annotation has the same runner/server communication-loss diagnostic; its human consolidation explicitly includes Windows smoketest shards with unavailable logs. OPEN-only searches for Windows, runner, and lost-communication diagnostics also found #5821, which shows the same dependency-install interruption. The open-root timelines show 28 distinct actual incoming duplicate relationships for #5799 versus 0 for #5821 (not ordinary mentions; no closed tickets searched or inspected). #5799 is the established, older canonical root. The affected shard and runner differ; the specific infrastructure symptom matches.
Proposed operations
Dry run — proposal only: close this ticket as a canonical duplicate of #5799. No title or team operation is proposed when closing as a duplicate. No state, duplicate relationship, title, team, labels, or project changes applied; the existing root is untouched. The #6300-specific auto-approval does not authorize this different root.