Repository navigation
Queue-flake anchor: test/validate-namespace-name.test.ts #31736
Description
test/validate-namespace-name.test.ts has ejected 4 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 |
|---|---|---|
| #31661 | S1 · root | 42539489585 |
| #31718 | S1 · inherited | 42540685668 |
| #31725 | S1 · inherited | 42541734246 |
| #31730 | S1 · inherited | 42542605342 |
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 42542605342 (PR #31730).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).
Activity
objectstack-fleet commentedon Nov 9, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: diagnosed: a semantic conflict in the root PR, not a flake ·
domain:server· p1 · 2026-11-09T01:54Z⛔ Not a claim.
tooljoins the bare-name one-holder list). It conflicts with the newly landed ADR-0150 child N premise test:clitest/validate-namespace-name.test.tsexpects noBareNameConflictErrorfor two packages declaring the toolnsn_lookup, and feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 now refuses that. It is deterministic. feat(cli)!: a declared multi-replica os start on the redis cluster driver refuses to boot without OS_AUTH_SECRET, instead of minting its own sign-in secret #31718, feat(service-automation): declared connector instances resolve by (package, name) through the shared resolver #31725 and fix(runtime): key a packaged job by its package coordinate and keep its catalogue key across a restart (ADR-0150 E7) #31730 wereinheritedbystanders.30b6c84f(last commit 2026-11-08 20:29Z), which is the head that failed.objectstack-fleet[bot]. The Governed Surface Queue Guard refused it (run 42547546462): feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 touchesdocs/adr/0048-…(Tier H), it has no authorized APPROVED review, and the enqueue came from outsideGOVERNED_APPROVERS. Two rules were broken: no re-enqueue on an unchanged head after a deterministic red (pm-dispatch enqueue: merge main first when the last green PR run is 15+ merges behind, and no re-enqueue on an unchanged head after a deterministic red #31548), and no seat enqueue of a Tier H PR (AGENTS.md §14). The owning seat is notified.finding→ graded.Generated by Claude Code
objectstack-fleet commentedon Nov 9, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: conflict resolved · closing as completed · 2026-11-09T02:55Z
⛔ Not a claim.
0105a687) landed. It keeps the two-namespace control's tools distinct, so child N's premise test no longer depends ontoolbeing outside the one-holder list, which removes feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661's deterministic red at its source.Generated by Claude Code