You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI flake - Windows self-hosted runner loses communication with GitHub #5799
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
Upload build artifacts (Windows)
Error:
Could not fetch job logs: Command '['gh', 'api', '-X', 'GET', 'repos/clockworklabs/SpacetimeDB/actions/jobs/97516734534/logs']' returned non-zero exit status 1.
Exact linked job: run 32752874810, job 97516734534, attempt 2.
Exact-job logs return HTTP 404; the failure is not diagnosable from the detector's log-fetch error alone. The exact check annotation instead says the self-hosted runner lost communication with the server. Runner ghr-ea9685f3 ran 16:57:40–17:08:41 UTC on 2026-08-24. This establishes runner loss, not an artifact-upload assertion. Host termination, CPU/memory starvation, and network interruption are possibilities named by GitHub, not proven causes.
Duplicate selection
Keep this ticket as the human-consolidated Windows runner-loss/unavailable-log root. Open #5821 has the same explicit runner-loss annotation and already identifies this tracker; do not reverse the established root or reorganize it.
Proposed operations
Dry run — proposals only. Keep this ticket open. Proposed title: CI flake - Windows self-hosted runner loses communication with GitHub. Proposed team: DevOps, for runner lifecycle/connectivity. Preserve the human consolidation. No title, team, state, label, project, or duplicate changes applied.
changed the title [-]CI flake - Windows job logs cannot be retrieved[/-][+]CI flake - Windows self-hosted runner loses communication with GitHub[/+]on Oct 28, 2026
Applied your approval: renamed this issue to CI flake - Windows self-hosted runner loses communication with GitHub. Verified it remains open with Team: DevOps in the Test flakes project. No other triage metadata changed.
Activity
5 remaining items
bfops commentedon Oct 20, 2026
Consolidated manifestations:
[-]CI flake: Upload build artifacts (Windows)[/-][+]CI flake - Windows job logs cannot be retrieved[/+]clockwork-labs-bot commentedon Oct 26, 2026
Symptoms and root cause
Exact linked job: run
32752874810, job97516734534, attempt2.Exact-job logs return HTTP
404; the failure is not diagnosable from the detector's log-fetch error alone. The exact check annotation instead says the self-hosted runner lost communication with the server. Runnerghr-ea9685f3ran 16:57:40–17:08:41 UTC on 2026-08-24. This establishes runner loss, not an artifact-upload assertion. Host termination, CPU/memory starvation, and network interruption are possibilities named by GitHub, not proven causes.Duplicate selection
Keep this ticket as the human-consolidated Windows runner-loss/unavailable-log root. Open #5821 has the same explicit runner-loss annotation and already identifies this tracker; do not reverse the established root or reorganize it.
Proposed operations
Dry run — proposals only. Keep this ticket open. Proposed title:
CI flake - Windows self-hosted runner loses communication with GitHub. Proposed team: DevOps, for runner lifecycle/connectivity. Preserve the human consolidation. No title, team, state, label, project, or duplicate changes applied.bfops commentedon Oct 28, 2026
@clockwork-labs-bot go ahead with the proposed changes
[-]CI flake - Windows job logs cannot be retrieved[/-][+]CI flake - Windows self-hosted runner loses communication with GitHub[/+]clockwork-labs-bot commentedon Oct 28, 2026
Applied your approval: renamed this issue to CI flake - Windows self-hosted runner loses communication with GitHub. Verified it remains open with Team: DevOps in the Test flakes project. No other triage metadata changed.