Skip to content

fix(ci): two REQUIRED contexts sat behind a single self-hosted runner, and it went offline #1135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
avrabe wants to merge 1 commit into from
Closed

fix(ci): two REQUIRED contexts sat behind a single self-hosted runner, and it went offline #1135

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,18 @@ jobs:

fmt:
name: Format
runs-on: [self-hosted, linux, x64, light]
# SINGLE POINT OF FAILURE REMOVED (2026-09-02). This was
# [self-hosted, linux, x64, light], a pool with EXACTLY ONE runner
# (pulseengine-ci-01-8). That runner went offline and this job — a REQUIRED
# context — sat 600s and failed with ZERO steps executed, which blocks every
# merge in the repo: branch protection needs the context to PASS, and a
# dead pool cannot produce a pass. `Version Pin Sweep` was behind the same
# single runner, so TWO of the nine required contexts shared one machine.
#
# Moved to `lean-mem` (4 runners, all online and idle at the time of the
# move). The rule this encodes: a REQUIRED context must not depend on a
# single-runner pool. Capacity was never the problem — redundancy was.
runs-on: [self-hosted, linux, x64, lean-mem]
steps:
- uses: actions/checkout@v7
- uses: dtolnay/rust-toolchain@stable
Expand All @@ -161,7 +172,18 @@ jobs:

pin-sweep:
name: Version Pin Sweep
runs-on: [self-hosted, linux, x64, light]
# SINGLE POINT OF FAILURE REMOVED (2026-09-02). This was
# [self-hosted, linux, x64, light], a pool with EXACTLY ONE runner
# (pulseengine-ci-01-8). That runner went offline and this job — a REQUIRED
# context — sat 600s and failed with ZERO steps executed, which blocks every
# merge in the repo: branch protection needs the context to PASS, and a
# dead pool cannot produce a pass. `Version Pin Sweep` was behind the same
# single runner, so TWO of the nine required contexts shared one machine.
#
# Moved to `lean-mem` (4 runners, all online and idle at the time of the
# move). The rule this encodes: a REQUIRED context must not depend on a
# single-runner pool. Capacity was never the problem — redundancy was.
runs-on: [self-hosted, linux, x64, lean-mem]
steps:
- uses: actions/checkout@v7
# Issue #145: fail at PR time if [workspace.package].version drifts from
Expand Down
Loading