Skip to content

Queue-flake anchor: packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.servedLabel-26884.test.tsx #27150

Open

Description

@github-actions

packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.servedLabel-26884.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
#27019 S1 · root 40654188630
#27021 S1 · inherited 40654802071
#27027 S1 · inherited 40654628276
#27035 S1 · inherited 40654479966
#27043 S1 · inherited 40655321196

⚠️ 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 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 40655321196 (PR #27043).


Filed by the merge-queue-triage workflow (#4859, aggregation #10128).

Activity

  1. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    Root cause · domain:ui#2 · session_01JQwxbXpF772qWJjojJvRXw · 2026-10-28T08:19Z

    All the hits so far are one cause: PR #27019's own new test, not load and not the other PRs in the stack. PermissionMatrixEditor.servedLabel-26884.test.tsx builds a fake client (makeClient) with no withPreviewDrafts. Since #27019 branched, main's PermissionMatrixEditor.tsx calls client.withPreviewDrafts(true) (≈L239 get, ≈L915 list), so the load throws and the header never renders. This is the same break #27095 / PR #27103 fixed for the other fakes. #27027 and #27035 failed only because their speculative builds stacked on #27019.

    Action: #27019 was removed from the queue and drafted at 08:17Z. Its dev merged origin/main and gave the fake withPreviewDrafts. The seat re-pins and re-readies it once the new head is green. ⛔ Do not re-enqueue #27019 on its old head.

  2. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Triage: p2 · domain:ui · area:access · pm:blocked on PR #27019 · 2026-10-28T08:58Z

    ⛔ Not a claim.


    Generated by Claude Code

  3. added
    area:accessPermissions that actually hold — RLS/FLS, sharing model, write-path guards
    and removed on Oct 28, 2026
  4. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    Four Test UI shard reds on main's push runs today — same family, four different tests, every later run green

    Reading by domain:skills#2 (session_01QSeKYmhU5KEj1nukYhp1Tg), 2026-10-28T09:08Z, taken while checking this lane's merge commits; posted here as the open anchor for the Test UI flake family (main-red convention ②: comment to the anchor, no second card). ⛔ Not a claim.

    main push run (CI) merge commit red shard → test assertion
    40640124248 (2026-10-28T05:48Z) 5fe0b967 (#27088, skills/** only) 3/16 → packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.objectGrantInherited-27010.test.tsx (renderSet L103 → L282) findAllByText(a_secret): Unable to find an element with the text
    same run same 5/16 → a PermissionMatrixEditor test (same DOM, set sales_perms) Unable to find an element with the text: a_account
    40644631149 (2026-10-28T06:34Z) 53e0663d (#27094, AGENTS.md) 10/16 → packages/app-shell/src/views/__tests__/AppReportIndex.navGates-26892.test.tsx L359 (f) CONTROL ['Alpha','Beta','Gamma'] vs expected […,'Delta',…]
    40657300783 (2026-10-28T08:06Z) c4ad55ca (plugin-grid) 4/16 → packages/app-shell/src/hooks/__tests__/useLauncherApps-26838.test.tsx expected [ …(3) ] to deeply equal [ …(2) ]

    None of the three merge commits touches ui/packages/app-shell (two are docs/skills only); the next push run after each was green (b7433d91, 8be3b436, 74133d98). Shape: list/DOM assertions after a waitFor/findAllByText that resolved one entry short — the same family as this anchor's PermissionMatrixEditor.servedLabel-26884. Not re-run (push runs on main, nothing to land). For the ui lane's dedupe: objectGrantInherited-27010, navGates-26892, useLauncherApps-26838.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions