ci: parity-main on the release runner, not behind PR parity jobs

The queued parity-main run waited 2 h behind PR parity jobs on the two
horizon-game runners, each merge replacing the pending one, and releases
need it green. The release runner gets a horizon-parity-main label; a
release only starts after parity-main passed, so the two never compete.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
Ludovic MarieandClaude Opus 5.5 committed 2026-10-26 03:10:55 +01:00
1 parent 74b08e6310
commit 2c612fd791
1 file changed
+5 -3
+5 -3
View File
@@ -23,9 +23,11 @@ env:
jobs:
parity-main:
# The Mac mini's runners only: a desktop job slowed down because the maintainer came back could time out, and a
# failure here bisects and comments on merges.
runs-on: [self-hosted, horizon-game, macOS]
# The Mac mini's release runner (label added 2026-10-26), not the two `horizon-game` runners: behind PR parity jobs
# this run waited 2 h while every merge replaced the pending one, and releases wait for it. Releases need it green
# first, so the two never compete. Not the desktop: a job slowed down because the maintainer came back could time
# out, and a failure here bisects and comments on merges.
runs-on: [self-hosted, macOS, horizon-parity-main]
timeout-minutes: 240 # a core-crate batch reruns ~300 harnesses (~60-90 min), a bisect a few rounds of the failures
steps:
- uses: actions/checkout@v4