ci(runner): macOS Intel runner auto-reregister watchdog - #332
Merged
Conversation
frstrtr
marked this pull request as ready for review
June 22, 2026 16:22
frstrtr
added a commit
that referenced
this pull request
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the second half of runner hardening (auto-reregister on drop).
The launchd service on macpro-intel-204 already has KeepAlive(SuccessfulExit=false), which restarts a crashed runner process. That cannot recover a runner GitHub has deregistered server-side (registration removed / token revoked) — re-registration needs a fresh registration token minted with repo-admin creds, which live on the CI bridge, not the Mac node.
This adds scripts/ci/runner-watchdog-mac-intel.sh, intended to run on the bridge (cron/launchd, ~5min poll). It polls the runners API and, after THRESHOLD consecutive offline observations, mints a fresh token and re-registers over SSH via config.sh --replace (no delete), then reloads the service. Idempotent; resets on first online sighting.
Revert: delete the file + remove its bridge cron/launchd entry. Only mutation is config.sh --replace (reuses same runner name).
Follow-up (not in this PR): install the bridge cron/launchd entry; arm64 .227 equivalent.
Draft pending operator merge-gate.