Skip to content

4-hourly full run: red on main (CI) #26457

Closed

Description

@github-actions

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

4-hourly full run: red on main (CI)

Swept 2026-10-27T04:19:52.772Z · run log · commit 26e7c75e9ae232237ae5f7caf6c23164652853b5 · conclusion failure.
CI runs the FULL battery on main every 4 hours (#16467, #25771). 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 scheduled 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 4-hourly run green.
Fix what it names and let the next 4-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 4-hourly run

Range: e843b5b320 (run 40424746941, the last green CI schedule run) .. 26e7c75e9a — compare

Activity

  1. added
    bugSomething isn't working
    priority:p1High: required for production / M2
    domain:devxDomain lane — seat card indexed by label:pm:seat
    on Oct 27, 2026
  2. objectstack-fleet commented on Oct 27, 2026

    @objectstack-fleet
    Contributor

    devx seat 2 · reading, not a claim. The red in run 40447801748 (schedule, head 26e7c75e) is one job, Test UI (1/16): the two doc-version-claims node-version: count assertions (expected 1 >= 15). That is the .nvmrc fallout of #26419, fixed by #26432 (#26421), which merged at 04:12Z as 67461403, after this run's head. On 67461403 the push CI run 40448487170 and the merge-group run 40447450044 are green, Test UI 16/16. No fix to dispatch. This card closes when the next 4-hourly scheduled CI run on main (about 08:05Z) is green; seat 2 watches it, and if that run is red for anything else, the card is dispatched as an ordinary devx card. It does not block 18.2: release.yml's full-battery gate reads the newest schedule or push CI run at or before the version commit.


    Generated by Claude Code

  3. objectstack-fleet commented on Oct 27, 2026

    @objectstack-fleet
    Contributor

    Triage: pm:on-hold until the next 4-hourly run · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-27T04:54Z

    ⛔ Not a claim.

    Restart-when: the next 4-hourly CI schedule run (about 08:05Z) is red. If it is green, that run closes this card.


    Generated by Claude Code

  4. added
    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterate
    pm:on-holdDecision made, deliberately deferred — no dispatch, no nag; restart condition in the hold comment
    on Oct 27, 2026
  5. objectstack-fleet commented on Oct 27, 2026

    @objectstack-fleet
    Contributor

    The 08:05Z scheduled full run on main is green: CI 40471268406 on ab3c776a, 39 of 39 jobs success, including all 16 Test UI shards and Test Core. The red this card tracked was #26419's .nvmrc move, fixed by #26432 (reading 6433856821). Closed by devx seat 2 (#20163).


    Generated by Claude Code

  6. removed
    pm:on-holdDecision made, deliberately deferred — no dispatch, no nag; restart condition in the hold comment
    on Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratebugSomething isn't workingdomain:devxDomain lane — seat card indexed by label:pm:seatpriority: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