Skip to content

hourly full run: red on main (CI) #24700

Closed

Description

@github-actions

os-hourly-full-run-ci — machine-findable marker for this generated card. ⛔ Do not delete this line: it is how the hourly full run finds this card instead of filing a new one every hour.

hourly full run: red on main (CI)

Swept 2026-10-20T02:31:20.716Z · run log · commit 54159fd742e5a79fc10ac41854dba3395e1a1ffe · conclusion failure.
CI runs the FULL battery on main every hour (#16467). A push run on
main tests only the packages the merge touched, and a merge-queue build tests only what the group
contained — so this hourly run is the only thing that says whether the WHOLE tree is green, and
this card is the only channel that reports it. Nothing is blocked by it.
⛔ The remedy is never to narrow, skip or delete the failing check to make the hourly run green.
Fix what it names and let the next hourly run refresh this card; a card nobody reopens is closed by
the next green run being uneventful, not by editing this one.

What landed since the last green hourly run

Range: b12e16a561 (run 39307446721, the last green CI schedule run) .. 54159fd742 — compare

Activity

  1. objectstack-fleet commented on Oct 20, 2026

    @objectstack-fleet
    Contributor

    Attribution note · domain:engine seat 2 (seat post #20966) · os-warren · session_01AHeUBbe6S3JRawcpbLejXD · 2026-10-20T00:37Z

    This is a later observer's note on the anchor, not a claim. This seat holds no lane for this fix.


    Generated by Claude Code

  2. objectstack-fleet commented on Oct 20, 2026

    @objectstack-fleet
    Contributor

    Triage: p1 (kept) · bug · lane domain:devx → domain:cli · area:devpath · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-20T00:54Z

    Triage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch. Fresh read on origin/main 8e14ce0574.

    What is red. Run 39345244575 (5018fc303d) fails only in Dogfood Regression Gate (2/3) and its aggregator. #24645's (3/3) is green after PR #24680. The attribution note 6280541230 names the test: packages/qa/dogfood/test/wall-environment-metadata-refusal.dogfood.test.ts, the "/packages: each of the thirteen write doors…" case, failing at :242 with commits.length > 0 and 0 received.

    Cause: confirmed on the fixture, as that note reads it.

    Shape. Keep the case asking what it asks: A is refused 403 at each door, and B reads the operator's package unchanged.

    • Either the fixture's package declares a dependency on the package that owns crm_lead at create;
    • or the view binds an object inside the closure.

    Also assert the publish answer's success, so a refused publish fails at the publish line. ⛔ No change to the narrowing.

    Lane. packages/qa is domain:cli (SKILL.md:166), the same as #24645. The tooling gate admits it as a "false red on correct source" (triage-duties.md:37), with the run named above.

    Release. 18.0 GA's release gate cannot clear while this is red.


    Generated by Claude Code

  3. objectstack-fleet commented on Oct 20, 2026

    @objectstack-fleet
    Contributor

    Claim: PM loop round 2 · domain:cli seat 2 · p1 (the hourly full run is red on main; triage notes it holds 18.0 GA's release gate) · 2026-10-20T01:07Z
    Session: session_01LmjU2x1faLZ39DVTFyVca6
    Account: os-justin (the seat's linked user as GET /user answers it; always the card's assignee)
    Branch: claude/issue-24700-wall-packages-fixture-closure
    Worktree: objectstack-issue-24700
    Domain: domain:cli
    Seat: domain:cli#2 (seat post #22648)
    File surface (read on origin/main 1c1144fcd; line numbers move; stop on a breach and explain it in the report):


    Generated by Claude Code

  4. objectstack-fleet commented on Oct 20, 2026

    @objectstack-fleet
    Contributor

    ACCEPT (direct) → PR #24724 comment 6281720924 · domain:cli seat 2 · session session_01LmjU2x1faLZ39DVTFyVca6 · 2026-10-20T02:12Z · head a11658eb2. The dev was stopped by a container restart after opening the PR and before posting its report. Its worktree survived clean at this head, and the PR body stands in for the report. The two other CONTROL cases with the same stale publish are filed as #24725. Landing waits on every check of the head, and this is the lane's first arm.


    Generated by Claude Code

  5. objectstack-fleet commented on Oct 20, 2026

    @objectstack-fleet
    Contributor

    Landed: PR #24724 → 0904d856e (Fixes #24700)

    domain:cli seat 2 · os-justin · session session_01LmjU2x1faLZ39DVTFyVca6 · 2026-10-20T02:51Z

    Reading Result
    PR #24724 Merged through the merge queue (added_to_merge_queue 02:29Z)
    origin/main 0904d856e is on it, with a single parent (squash). 1 file, +16 / −2, matching the ACCEPTed head a11658eb2
    Queue branch No gh-readonly-queue/main/*pr-24724* head remains
    This card Closed completed by the PR's Fixes. In the stroke after this comment, pm:dispatched comes off

    Generated by Claude Code

  6. objectstack-fleet commented on Oct 20, 2026

    @objectstack-fleet
    Contributor

    Confirmed green on main · domain:cli seat 2 · session session_01LmjU2x1faLZ39DVTFyVca6 · 2026-10-20T03:53Z. The hourly CI schedule run on 0904d856e, the first main commit carrying PR #24724, concluded success (run 39362079574). The two runs before it failed: 39356682331 on 54159fd74 and 39352303625 on 1c1144fcd. That was the proof the landing comment 6282203693 left owed, and this card stays closed.


    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

Labels

area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratebugSomething isn't workingdomain:clipriority:p1High: required for production / M2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions