Skip to content

CI flake - Windows self-hosted runner loses communication with GitHub #5799

Open

Description

@clockwork-labs-bot

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.

Failed job runs:

Timeout detection:

  • none

Context:

  • none

Activity

  1. 5 remaining items

  2. bfops commented on Oct 20, 2026

    @bfops
    Collaborator

    Consolidated manifestations:

  3. changed the title [-]CI flake: Upload build artifacts (Windows)[/-] [+]CI flake - Windows job logs cannot be retrieved[/+] on Oct 20, 2026
  4. clockwork-labs-bot commented on Oct 26, 2026

    @clockwork-labs-bot
    ContributorAuthor

    Symptoms and root cause

    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.

  5. bfops commented on Oct 28, 2026

    @bfops
    Collaborator

    @clockwork-labs-bot go ahead with the proposed changes

  6. 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
  7. clockwork-labs-bot commented on Oct 28, 2026

    @clockwork-labs-bot
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions