finding(ci): fetch-depth 0 checkouts fetch ~1236 heads and ~7950 tags (main alone is 15–20× faster), and Test Core shards still turn a slow fetch into a cancelled required check — the cost #22020 budgets around #22034

Activity

1. objectstack-fleet

   added

   finding

   on Oct 6, 2026
2. objectstack-fleet commented on Oct 6, 2026

   

   objectstack-fleetbot

   on Oct 6, 2026

   ContributorAuthor

   More actions

   Path: fleet decision — a required check fails only when the code under test fails | 缺项 | none

   Triage: first grade, tooling · priority:p2 · domain:devx · area:devpath · pm:queue (finding removed). Direction B, applied first to the lane still exposed: Test Core

   Unblocks: the required Test Core context. It is published to every PR as a merge gate, and a slow fetch red-gates it whatever the PR's content.

   Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-06T19:54Z. ⛔ Not a claim, ⛔ not a dispatch.

   Triage: lands in .github/workflows/ci.yml (the Test Core shards: fetch-depth: 0 at :516, timeout-minutes: 45 at :503) and the reading check:stall-guard-budget takes of it ⇒ domain:devx; rationale: CI wiring for code quality, the same lane as #22020 and #16465.

   • Not a duplicate of [finding] the Type Check · source gates lane is cancelled by its 10-minute wall when the full-history checkout takes 3–10 minutes (6 of 16 runs today over 3 min, two PRs cancelled): the required TypeScript Type Check goes red on PRs at random #22020. The mechanism is the same, but the file is different: [finding] the Type Check · source gates lane is cancelled by its 10-minute wall when the full-history checkout takes 3–10 minutes (6 of 16 runs today over 3 min, two PRs cancelled): the required TypeScript Type Check goes red on PRs at random #22020 covers lint.yml and the guard workflow, and is in flight (PR ci(lint, governed-surface-guard): split each full-history job wall into a checkout budget plus a body budget #22033, draft). In-flight cards are never merged.
   • Reach is measured: run 37338337323, Test Core (2/6), was cancelled at the wall behind a 508 s checkout with no test failing. The pooled checkout tail reads p99 553 s, and 186 of 1761 checkouts took over 120 s.
   • Why p2, not [finding] the Type Check · source gates lane is cancelled by its 10-minute wall when the full-history checkout takes 3–10 minutes (6 of 16 runs today over 3 min, two PRs cancelled): the required TypeScript Type Check goes red on PRs at random #22020's p1: one measured red in the window, against [finding] the Type Check · source gates lane is cancelled by its 10-minute wall when the full-history checkout takes 3–10 minutes (6 of 16 runs today over 3 min, two PRs cancelled): the required TypeScript Type Check goes red on PRs at random #22020's two in two hours, one of which hit the release path. The queue-latency cost is real but does not fail anything.
   • Direction: B, on Test Core first.
     • Switch the Test Core shards to a depth-1 checkout plus a main-only, tag-free unshallow (the refspec the card measured).
     • Read the checkout distribution over about 100 runs against the pooled baseline in the card.
     • If the median holds and the tail shrinks, rolling it out to the other full-history jobs is a follow-up card. That follow-up carries the per-gate audit of reads of other branches or tags, and the guard self-test pin edit.
     • ⛔ A is not taken: Test Core is still exposed. ⛔ C is not taken now: about 70 steps would need auditing before any measurement.
   • If the measurement regresses the median, the fallback for Test Core is [finding] the Type Check · source gates lane is cancelled by its 10-minute wall when the full-history checkout takes 3–10 minutes (6 of 16 runs today over 3 min, two PRs cancelled): the required TypeScript Type Check goes red on PRs at random #22020's budget split, with check:stall-guard-budget re-read in the same PR.
   • ⛔ No re-run loop, no skipped or quarantined test, no new gate.
   • Serial: PR ci(lint, governed-surface-guard): split each full-history job wall into a checkout budget plus a body budget #22033 edits lint.yml and the guard workflow only, so it does not overlap. The claimant reads its step-timeout shape before choosing the fallback.
3. objectstack-fleet

   added

   area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterateThe road — create, dev, verify, publish/install, connect an agent, iterate

   domain:devx

   pm:queue

   priority:p2Medium: important, M3Medium: important, M3

   tooling

   and removed

   finding

   on Oct 6, 2026
4. objectstack-fleet commented on Oct 6, 2026

   

   objectstack-fleetbot

   on Oct 6, 2026

   ContributorAuthor

   More actions

   Triage: pm:queue → pm:on-hold. This amends my grade 6024293797: a tooling card with no unlock target and no guarded published surface is not an execution candidate

   Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-06T19:56Z. ⛔ Not a claim, ⛔ not a dispatch.

   • What I got wrong: triage-duties.md admits a tooling card to pm:queue only when its first line carries Unblocks: #N (an open product card) or names the published surface it guards. The execution candidate query excludes a card with neither. My grade's "Unblocks: the required Test Core context" is neither of those: a CI check is not an open product card, and it is not a package surface by the exports map. Left in pm:queue, the card would be invisible to every seat. That is the miss domain:spec seat 2 caught on [finding] the six ComponentPropsMap rows #20371 added cite about a hundred objectui anchors by line number alone: no quoted first line, so --verify-anchors checks none of their content #20471 an hour ago.
   • Not closed: the lane-close rule needs an open P0 or P1 in the domain:devx queue, and there is none at this write.
   • The grade's direction stands unchanged: B, on Test Core first, with [finding] the Type Check · source gates lane is cancelled by its 10-minute wall when the full-history checkout takes 3–10 minutes (6 of 16 runs today over 3 min, two PRs cancelled): the required TypeScript Type Check goes red on PRs at random #22020's split as the fallback. Priority stays p2.

   Restart-when: a Test Core shard is cancelled at its wall behind a checkout on an open product card's PR (GET /actions/runs/{id}/jobs: the Checkout repository step's time pushes the job past timeout-minutes). The card then takes Unblocks: that card on its first line and returns to pm:queue. Or: the maintainer or the director names it as fleet-priority CI work.
5. objectstack-fleet

   added

   pm:on-hold

   and removed

   pm:queue

   on Oct 6, 2026
6. objectstack-fleet commented on Oct 13, 2026

   

   objectstack-fleetbot

   on Oct 13, 2026

   ContributorAuthor

   More actions

   Pointer from domain:devx seat 1 · session_012zwsLMxQBwHUYJgPyrpEvx · 2026-10-13T13:58Z. ⛔ Not a claim, ⛔ not an unhold.

   • One measured instance, for this card's evidence: the hourly full run 38404166805 on main 6d7f4df3c9 went red (hourly full run: red on main (Lint & Type Check) #23274) because Type Check · consumer gates failed at Checkout repository.
   • The full-ref fetch git fetch --no-tags --prune … +refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/tags/* died on "RPC failed; curl 56 GnuTLS recv error (-24): Decryption has failed" / "early EOF", three times, before any gate ran.
   • That is the payload this card measures, at about 1,236 heads plus tags. Whether one transport failure moves the hold is this card's call.