From dfa61a294e10a0b0d8249f0f89813e811b4b3e10 Mon Sep 17 00:00:00 2001 From: REPPL <77722411+REPPL@users.noreply.github.com> Date: Sun, 18 Oct 2026 18:13:25 +0100 Subject: [PATCH] chore: capture the macOS leg's headroom and record a falsified ground Across nine merge-group runs on 2026-10-18 the check job's macOS leg took 35.2 to 49.4 minutes, the run of #1099 within 0.6 minutes of its 50-minute warning; nearly all of it is the one race-enabled pass. Captured, minor, so the leg is tracked before the warning fires. The loop-speed record's grounds named what would show them wrong, a merge-group race step no shorter than before, and the first two runs after both of its changes showed it: the ubuntu race step took 20.8 and 20.6 minutes, at the top of its earlier range. The record now says so; its cut in git processes stands where it was measured and is below the difference between runners on CI. Refs: iss-2610181711260494 Refs: iss-2610180545134593 Assisted-by: Claude:claude-opus-5-5 --- ...260494-the-check-job-s-macos-leg-has-little.md | 15 +++++++++++++++ ...4593-the-implement-loop-package-s-tests-are.md | 4 ++++ 2 files changed, 19 insertions(+) create mode 100644 .abcd/work/issues/open/iss-2610181711260494-the-check-job-s-macos-leg-has-little.md diff --git a/.abcd/work/issues/open/iss-2610181711260494-the-check-job-s-macos-leg-has-little.md b/.abcd/work/issues/open/iss-2610181711260494-the-check-job-s-macos-leg-has-little.md new file mode 100644 index 0000000000..3a9e341e65 --- /dev/null +++ b/.abcd/work/issues/open/iss-2610181711260494-the-check-job-s-macos-leg-has-little.md @@ -0,0 +1,15 @@ +--- +schema_version: 1 +id: "iss-2610181711260494" +slug: "the-check-job-s-macos-leg-has-little" +severity: "minor" +category: "process" +source: "agent-finding" +found_during: "manual-capture" +origin: researcher-authored +production_mode: hand-written +found_at: ".github/workflows/ci.yml" +remedy: "Shorten the macOS race pass below about 40 minutes on a slow runner, starting from its slowest packages (internal/core/implement/loop, internal/surface/cli, internal/core/claim), or ask the technical facilitator to raise the macOS ceiling and warning with the spread as the evidence" +--- + +The check job's macOS leg has little headroom before its 50-minute warning: across nine merge-group runs on 2026-10-18 it took 35.2, 36.5, 38.9, 42.3, 42.4, 43.0, 43.9, 49.4 and 44.8 minutes, and the run of #1099 came within 0.6 minutes of the warning. Nearly all of it is the one race-enabled pass over the whole module, 41.9 to 47.4 minutes in the last three; the plain-only guard step after it takes under a minute. The warning fires at 50 and the job ceiling is 60. diff --git a/.abcd/work/issues/resolved/iss-2610180545134593-the-implement-loop-package-s-tests-are.md b/.abcd/work/issues/resolved/iss-2610180545134593-the-implement-loop-package-s-tests-are.md index 03dfab074e..5b9c428c3a 100644 --- a/.abcd/work/issues/resolved/iss-2610180545134593-the-implement-loop-package-s-tests-are.md +++ b/.abcd/work/issues/resolved/iss-2610180545134593-the-implement-loop-package-s-tests-are.md @@ -19,3 +19,7 @@ The implement loop package's tests are bound by git subprocesses: the slowest, T ## Grounds - pursued: the loop package's tests and every drain move spend about a quarter fewer git processes, so the ubuntu leg's race step shortens by a minute or more; a merge-group race step no shorter than before would show it wrong + +## Outcome + +The grounds were shown wrong on the first two merge-group runs after both changes (#1099, #1100, 2026-10-18). The ubuntu leg's race step took 20.8 and 20.6 minutes, at the top of the 14 to 20.6 minutes it had taken before, not a minute shorter. Its package times summed to 4,293 and 4,243 CPU-seconds, against 4,254 at the slowest run before. The loop package took 635 and 621 seconds under race, inside its earlier 470 to 650. The cut in git processes stands where it was measured (one drain test, 1,107 to 830), but on CI it is below the difference between runners. The leg's remaining time is tracked in iss-2610181711260494.