Skip to content

ci-fix: transient macOS runner communication loss on run 32960945674 #6236

Description

@prql-bot

Failure

tests run 32960945674 (scheduled nightly on main, commit d63e957) — one job failed: nightly / nightly-release / build-prqlc-c (macos-15, aarch64-apple-darwin).

Diagnosis

Transient hosted-runner death, not a code or workflow fault. The job's single annotation is GitHub's runner-loss message, and the log blob was never uploaded:

The hosted runner lost communication with the server. Anything in your workflow
that terminates the runner process, starves it for CPU/Memory, or blocks its
network access can cause this error.
$ gh api repos/PRQL/prql/actions/jobs/98152972844/logs
<Error><Code>BlobNotFound</Code>...
$ gh api repos/PRQL/prql/actions/jobs/98152972844 --jq '[.steps[] | {name, conclusion}]'
# every step after "📂 Checkout code" has conclusion: null

Supporting evidence:

  • Duration is the tell. The leg ran 11:07:03 → 11:55:03 (48 min) before being declared dead. The same job took 9m53s, 10m02s and 6m39s on the three preceding nights, and the non-nightly build-prqlc-c (macos-15, aarch64-apple-darwin, default,test-dbs) leg in this very run finished in 3m42s and passed.
  • No relevant change. The triggering commit (#6233) touches only CHANGELOG.md, web/playground/package.json, package-lock.json, src/main.jsx and src/reportWebVitals.js — nothing reachable from a Rust aarch64-apple-darwin C-bindings build.
  • Clean history. The 11 preceding scheduled tests runs on main (2026-08-15 → 2026-08-25) all concluded success.
  • Isolated. Every other job in the run passed; the three sibling build-prqlc-c targets (ubuntu x86_64-musl, ubuntu aarch64-musl, windows msvc) all passed.

Resolution

Reran the failed job. Attempt 2 completed in 10m04s (11:58:37 → 12:08:41) and the run now concludes success with 0 failing jobs, so main is green again.

No repeat-occurrence escalation applies — the most recent prior transient tracker is #6188 (2026-08-12, a setup-task download failure), outside the 7-day window and a different failure shape.

Metadata

Metadata

Assignees

No one assigned

    Labels

    tend-outageTracks bot outage incidents

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions