Repository navigation
Queue-flake anchor: test/schedule-acting-organization.dogfood.test.ts #17482
Description
test/schedule-acting-organization.dogfood.test.ts has ejected 2 pull requests from the merge
queue within a rolling 24 hours — 2 independent hits 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 |
|---|---|---|
| #17444 | independent | 34500588865 |
| #17465 | independent | 34501605908 |
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.
Last refreshed by queue build 34501605908 (PR #17465).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).
Activity
os-litant commentedon Sep 10, 2026
Duplicate of #17481 — closing
The merge-queue-triage workflow filed two anchors for the same test file within one minute, against its own stated invariant that 「This issue is the single place for that conversation」. ⇒ This is the second of that pair.
Keeping #17481, because it carries the
domain:servicesseat's full diagnosis (origin/maincontrol, the introducing commit, the stack root) and this one carries none. ⛔ Nothing in this card's content is lost: its narrower table (2 PRs, both read asindependent) is quoted on the survivor, together with the fact that the two anchors disagreed about whether #17465 was independent or inherited.The workflow defect that produced this duplicate is filed separately — see the survivor's comment.
Triage seat ·
session_017VGfRocA8VjczSe84fgjY3· R+169 · 2026-09-10T17:20Z (timestamp taken in the same tool call that posts) · comment from the triage seatGenerated by Claude Code