Skip to content

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

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-02T10:18:04.799Z · run log · commit ee75aae1a8ebc2625e57074527d446151535634b · 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: bbe03f4068 (run 36705938370, the last green CI schedule run) .. ee75aae1a8 — compare

Truncated by the compare API; open the compare link for the full list.

Activity

  1. objectstack-fleet commented on Oct 2, 2026

    @objectstack-fleet
    Contributor

    Triage: pm:on-hold — the run died in install, before any test body ran. The next hourly run decides

    Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-02T10:57Z. ⛔ Not a claim, ⛔ not a dispatch.

    Restart-when: the next scheduled CI run on main after run 36993106033 concludes failure.

    What failed (read now, run 36993106033):

    • One job, Test Core (5/6), failed at Install dependencies. Verify test shard results then reported the missing shard.
    • Two infrastructure faults happened at once:
      • The pnpm store cache missed on the same key that hit an hour earlier, in the green run 36987362777.
      • So better-sqlite3@13.0.3 built from source, and node-gyp's one fetch of the Node headers from nodejs.org was reset (ECONNRESET).
    • No test ran. The 09:01 scheduled run was green, on 3937ad2f32.

    Why hold, not dispatch. No code fault is named. The class is "died before any test body ran", so the next scheduled run is the reading:

    • Green: this card closes itself, as its header says.
    • Red: this hold releases, and the cause is read from that run.

    If it recurs at install: the hardening direction is that the install stops fetching Node headers over the network on a store-cache miss. For example, node-gyp is pointed at the runner's own Node installation in .github/actions/setup-pnpm. That is CI wiring, so it routes to domain:spec by the anchoring exception. ⛔ No step is skipped or narrowed.


    Generated by Claude Code

  2. objectstack-fleet commented on Oct 2, 2026

    @objectstack-fleet
    Contributor

    Triage: closed completed — the next scheduled run is green, and the red was an install-step fault with no test run

    Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-02T11:55Z. ⛔ Not a claim, ⛔ not a dispatch.

    • The reading the hold waited for (5950881330): the next scheduled CI run on main, run 36998660253 on 3b4efa74b2, concluded success at 2026-10-02T11:24Z, with every shard passing. So the hold's Restart-when: (a red run) did not fire.
    • What the red was: run 36993106033's only failure was Test Core (5/6) at Install dependencies, with no test run. A pnpm store cache miss was followed by a reset on node-gyp's Node-header fetch.
    • No code fault is named, so nothing remains on this card. If a later hourly run is red, the generator files a fresh card, and that run is read on its own.
    • If the install-step reset recurs, the hardening direction in 5950881330 is the starting point.

    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

    Labels

    bugSomething isn't workingdomain:devxpriority: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