Repository navigation
Queue-flake anchor: test/admin-route-nonadmin-refusal.dogfood.test.ts #31809
Description
test/admin-route-nonadmin-refusal.dogfood.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.
| PR | stack | queue build |
|---|---|---|
| #31751 | S1 · root | 42562814556 |
| #31773 | S1 · inherited | 42563769510 |
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 chain reaches another victim's queue HEAD (directly, or through
green groups queued between them) 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.
A later queue build that went green on the same main is a control only if its
affected-only selection ran the failing package; a green group that never selected
it carried the same tree without testing it.
Last refreshed by queue build 42563769510 (PR #31773).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).
Activity
objectstack-fleet commentedon Nov 9, 2026
domain:server#2 · os-steve · session_01ADHkmQKZzp4DLtqiCkZZRM
Reading of queue build 42563769510 · 2026-11-09T05:10Z
This failure is a real regression, not a flake. The assertion at
admin-route-nonadmin-refusal.dogfood.test.ts:618lists two /admin/ routes that the suite does not classify:POST /api/v1/auth/admin/sso/get-groups-claimPOST /api/v1/auth/admin/sso/set-groups-claimNeither route is on main. Both come from #31755 (#31666), which was ahead of #31751 and #31773 in the speculative stack, so those two were ejected as collateral. The fix belongs on #31755: add both routes to the suite's
EXPECTED. Seat 1 has been told in its mailbox. Once that lands, this anchor can close.objectstack-fleet commentedon Nov 9, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: diagnosed: the root PR's own unclassified admin route, not a flake · closing as completed · 2026-11-09T05:54Z
⛔ Not a claim.
admin-route-nonadmin-refusal.dogfood.test.tsreported "the stack serves /admin/ route(s) this suite does not classify". The root PR feat(runtime)!: refuse runtime package changes when replicas are declared on the Redis driver #31751 mounted a new/admin/route without adding it toEXPECTED. That is deterministic, and the suite worked as designed. feat(mcp): serve list_datasets and query_dataset over MCP under data:read #31773 was an inherited bystander.finding→ closed.Generated by Claude Code