Development record
2026-10-28 — facilitator-on-delegation: the coordinating session (abcd-f5), on delegation from the technical facilitator, raises the check job's macOS leg ceiling in ci.yml from 70 to 85 minutes and moves its warning line from 60 to 75, keeping it ten minutes ahead; the ubuntu leg stays at 45. On 2026-10-28 merge-group run 40752008734 (PR #1196) had check (macos-latest) cancelled after about 71 minutes, from 19:11:30Z to 20:22:05Z, and the queue dropped the group with failed_checks, while that day's passing merge-group runs took roughly 46 to 68 minutes. 85 stays below the merge queue's 90-minute check response timeout. The lasting remedy is still a faster suite: iss-2610181711260494 named it and was resolved by the raise to 70, and the faster race pass stays open as iss-2610181757540736; this resolves iss-2610282035340363.
2026-10-28 — facilitator-on-delegation: the coordinating session (abcd-f5), on delegation from the technical facilitator, raises the check job's macOS leg ceiling in ci.yml from 70 to 85 minutes and moves its warning line from 60 to 75, keeping it ten minutes ahead; the ubuntu leg stays at 45. On 2026-10-28 merge-group run 40752008734 (PR #1196) had check (macos-latest) cancelled after about 71 minutes, from 19:11:30Z to 20:22:05Z, and the queue dropped the group with failed_checks, while that day's passing merge-group runs took roughly 46 to 68 minutes. 85 stays below the merge queue's 90-minute check response timeout. The lasting remedy is still a faster suite: iss-2610181711260494 named it and was resolved by the raise to 70, and the faster race pass stays open as iss-2610181757540736; this resolves iss-2610282035340363.
Frontmatter
| id | dcn-2610282036219503 |
|---|---|
| type | decision |
| date | 2026-10-28 |
.abcd/work/decisions/dcn-2610282036219503-facilitator-on-delegation-the.md
open on GitHub ↗ · commit history ↗
mentions3
- iss-2610181711260494The 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.
- iss-2610181757540736The check job's race passes are set by their total work: the macOS pass keeps a steady 2.80 to 2.85 of its runner's three test slots busy and the ubuntu one about 3.4 of four, so no reordering shortens them, and their slowest packages (internal/core/implement/loop, internal/surface/cli, internal/core/claim, about 46% of the macOS pass) spend most of it in git processes. A first cut, a default-branch name per claim operation and a batched view (#1099, #1100), took one drain test from 1,107 git processes to 830 but the whole of the loop and claim packages only from 126,334 to 119,327 (5.5%), which CI could not tell from the difference between runners; a cut measured on one test overstates the package.
- iss-2610282035340363The macOS leg of the check job in ci.yml cancels merge-group runs at its 70-minute ceiling: on 2026-10-28 run 40752008734 (PR #1196's merge group) had check (macos-latest) cancelled after about 71 minutes, from 19:11:30Z to 20:22:05Z, and the queue dropped the group with failed_checks. That day's passing merge-group runs took roughly 46 to 68 minutes, so the leg runs near its cap and each cancel rebuilds every group queued behind it. The lasting remedy is a faster suite (iss-2610181711260494, resolved by the raise to 70, which named a faster race pass, iss-2610181757540736, as the longer lever).