Repository navigation
Queue-flake anchor: packages/app-shell/src/views/metadata-admin/DirectoryPage.stateVocabulary-29705.test.tsx #30253
Description
packages/app-shell/src/views/metadata-admin/DirectoryPage.stateVocabulary-29705.test.tsx has ejected 5 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 |
|---|---|---|
| #30225 | S1 · inherited | 41961141659 |
| #30226 | S1 · root | 41960860949 |
| #30240 | S1 · inherited | 41962230207 |
| #30242 | S1 · inherited | 41962404343 |
| #30246 | S1 · inherited | 41962336936 |
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 41962230207 (PR #30240).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).
Activity
objectstack-fleet commentedon Nov 5, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: first-touch audit · p2 ·
domain:ui·pm:queue· 2026-11-05T04:02Z⛔ Not a claim.
DirectoryPage.stateVocabulary-29705.test.tsx(Test UI) has ejected 4 PRs from the merge queue in 24 h (1 independent hit). A platform test that keeps going red is fixed, never skipped (「平台测试清单反复变红，肯定要修啊」), so p2.findingleaves the card now that it is graded.Generated by Claude Code
objectstack-fleet commentedon Nov 5, 2026
domain:ui#1 · os-support-ai · session_01WGufzfE4V9fzZgJLrLDmMC
Cause read · not a flake · 2026-11-05T04:22Z
⛔ Not a claim.
expected '可定制' to be '只读'on the page tile (queue build 41962336936, fix(core): compareTo on an already-past date range compares with the period before it, and previousYear from 29 February stays in February #30246's triage comment).797f9257, Studio: customize an installed package's page, so a customer can change a home or landing page without a code release #30063) opened Studio's Customize door forpage; fix(metadata-protocol,app-shell): serve a pair's mapping override, let a pair remove any override it holds, name a working remedy for an excluded type (#30062) #30226 (Declared overrides: a mapping override publishes but is never served, doc and mapping overrides cannot be restored, and an override's label can be hidden by translation #30062 item 4) changes the tile to follow the doors, and its first queue build still expected 只读. The serial note on Studio: customize an installed package's page, so a customer can change a home or landing page without a code release #30063 (6646961716) assigned the expectation flip to whichever PR landed second.c5033471("the tile follows the page and dataset Customize doors that landed on main") updates this test; auto-merge is armed. Every other row in the table is an inherited bystander (fix(core): compareTo on an already-past date range compares with the period before it, and previousYear from 29 February stays in February #30246 re-queued green and merged31260ca8).objectstack-fleet commentedon Nov 5, 2026
domain:ui#1 · os-support-ai · session_01WGufzfE4V9fzZgJLrLDmMC
Closed · cause fixed · 2026-11-05T05:24Z
#30226 merged
15f808ab4fat 2026-11-05T05:10:45Z with its headc5033471, which updatesDirectoryPage.stateVocabulary-29705.test.tsxto the page and dataset Customize doors #30233 opened. The ejections were that one semantic conflict (cause read above), not a flake; every other row was inherited. No test was skipped or quarantined.