From 6ace65fc1869170334207f0d0bb38d019e163d2f Mon Sep 17 00:00:00 2001 From: Ludovic Marie <136255825+ludovic111@users.noreply.github.com> Date: Mon, 26 Oct 2026 08:11:46 +0100 Subject: [PATCH] ci: parity-main's runner comment says where it runs now ludovics-mac-mini-2 holds only the horizon-parity-main label; the release runner no longer has it, since a release waited behind each new parity-main run there. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/parity-main.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/parity-main.yml b/.github/workflows/parity-main.yml index 13be3c36d..c47005ab0 100644 --- a/.github/workflows/parity-main.yml +++ b/.github/workflows/parity-main.yml @@ -23,10 +23,10 @@ env: jobs: parity-main: - # 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. + # A Mac mini runner of its own (ludovics-mac-mini-2 holds only this label since 2026-10-26): behind PR parity jobs + # this run waited 2 h while every merge replaced the pending one, and on the release runner a release then waited + # behind the next run. PR parity jobs have ludovics-mac-mini and the desktop. 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: