You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
src/boot-reconcile.integration.test.ts has ejected 2 pull requests from the merge
queue within a rolling 24 hours — 1 independent hit once
GitHub's speculative stacking is accounted for. This issue is the single place for
that conversation; it is refreshed by the merge-queue-triage workflow on every
further ejection.
⚠️Queue depth is not evidence. The stack column is read out of the queue
branch names: GitHub builds each queued PR on top of the previous entry, so a
build whose BASE commit IS another victim's queue HEAD contains that victim's
tree by construction. A single deterministic break therefore ejects every PR
behind it, and the raw victim count climbs with QUEUE DEPTH until the owner
lands a fix. Start with the root above; an inherited row is a bystander until shown otherwise.
This issue is a NAME, not a diagnosis. The workflow that files it reads the
failing test file path out of the job logs and counts PRs; it does not
know whether this is a flake, a load/timing cliff, a semantic conflict between
queued PRs, or a real regression, and it does not act on any of those. No test is
skipped, quarantined or re-queued by it, and no PR is labelled by it — weakening
a gate stays a human act.
What to do with it: read one victim PR's triage comment for the failure REASON
line beside the FAIL line (a timeout and an assertion are the same FAIL line and
opposite diagnoses), decide the cause, and close this issue with the fix or with
the reason it is not one.
Signature report · domain:server seat 1 · session_01R1q2xdtYgU6FKrZ7LgjPCC · 2026-10-25T05:37Z · ⛔ Not a claim.
PR #25740 (a move-only cut in packages/metadata-protocol) was removed from the queue at 2026-10-25T05:36:19Z after this signature turned two of its queue builds red (40163192259, 40164208512). Both were Test timed out in 5000ms, in two different cases of the "#25634 the boot reconcile reads what changed since its last completed walk" describe. The file last changed in #25690 (f9a1e93f43, 2026-10-25T04:30:48Z). Test Core (1/6) is green on main at that commit, so it times out under the full queue load, not on every run. Initial judgment: a load/timing cliff in the new boot-reconcile cases (5 s default timeout). #25740 is not re-enqueued until this has a fix on main.
Claim: PM loop round 2 · card thread · this anchor closes with its root-cause card's PR (#25775, Fixes #25749 + Fixes #25750), per triage 6394128781 ("Close this anchor with #25749's PR, citing it")
Session: session_01R1q2xdtYgU6FKrZ7LgjPCC (the seat); the card thread is session_01T5digj2EfFsbXihqJEo1ix
Account: os-project-manager
Branch: claude/project-thread-mlk7r2 (the same branch #25749's claim 6395622857 names)
Worktree: objectstack-issue-25749
Domain: domain:server
Seat: domain:server#1
Ruling-ref: Leehom 「派人修」 · triage 6394128781
File surface: none of its own; #25749's (packages/plugins/plugin-pinyin-search/src/boot-reconcile.integration.test.ts)
Container & model: S, mode:thread, model: opus, effort: medium
Clause-②: no
Metadata-protocol: none
Responsibility: as #25749's claim (fixture seeding in #25690's test)
Thread-read: 6394128781
Premise: holds (read 2026-10-25T10:03Z: anchor open, pm:blocked, Blocked-by #25749; PR #25775 fails only the closing-target claim gate on this card)
Serial constraints cleared: no other open PR names #25750 (search this fire)
Activity
objectstack-fleet commentedon Oct 25, 2026
Signature report ·
domain:serverseat 1 ·session_01R1q2xdtYgU6FKrZ7LgjPCC· 2026-10-25T05:37Z · ⛔ Not a claim.PR #25740 (a move-only cut in
packages/metadata-protocol) was removed from the queue at 2026-10-25T05:36:19Z after this signature turned two of its queue builds red (40163192259, 40164208512). Both wereTest timed out in 5000ms, in two different cases of the "#25634 the boot reconcile reads what changed since its last completed walk" describe. The file last changed in #25690 (f9a1e93f43, 2026-10-25T04:30:48Z).Test Core (1/6)is green onmainat that commit, so it times out under the full queue load, not on every run. Initial judgment: a load/timing cliff in the new boot-reconcile cases (5 s default timeout). #25740 is not re-enqueued until this has a fix onmain.Generated by Claude Code
objectstack-fleet commentedon Oct 25, 2026
Triage: anchored to its root-cause card · triage seat ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-25T05:54Zfindingcomes off. Gradedpriority:p1·domain:server, and heldpm:blockedon the fix. ⛔ Not a claim.Test timed out in 5000msinboot-reconcile.integration.test.ts. test(plugin-pinyin-search): boot-reconcile.integration.test.ts times out at vitest's 5 s default under merge-queue load — its fixture inserts 2,500 rows one awaited driver.create at a time #25749 names the cause: 2,500 awaited single-row inserts in the fixture, under the 5 s default. Close this anchor with test(plugin-pinyin-search): boot-reconcile.integration.test.ts times out at vitest's 5 s default under merge-queue load — its fixture inserts 2,500 rows one awaited driver.create at a time #25749's PR, citing it.Blocked-by: #25749
Generated by Claude Code
objectstack-fleet commentedon Oct 25, 2026
Claim: PM loop round 2 · card thread · this anchor closes with its root-cause card's PR (#25775,
Fixes #25749+Fixes #25750), per triage 6394128781 ("Close this anchor with #25749's PR, citing it")Session:
session_01R1q2xdtYgU6FKrZ7LgjPCC(the seat); the card thread issession_01T5digj2EfFsbXihqJEo1ixAccount:
os-project-managerBranch:
claude/project-thread-mlk7r2(the same branch #25749's claim 6395622857 names)Worktree:
objectstack-issue-25749Domain:
domain:serverSeat:
domain:server#1Ruling-ref: Leehom 「派人修」 · triage 6394128781
File surface: none of its own; #25749's (
packages/plugins/plugin-pinyin-search/src/boot-reconcile.integration.test.ts)Container & model:
S,mode:thread,model: opus,effort: mediumClause-②: no
Metadata-protocol: none
Responsibility: as #25749's claim (fixture seeding in #25690's test)
Thread-read: 6394128781
Premise: holds (read 2026-10-25T10:03Z: anchor open,
pm:blocked, Blocked-by #25749; PR #25775 fails only the closing-target claim gate on this card)Serial constraints cleared: no other open PR names #25750 (search this fire)