Skip to content

4-hourly full run: red on main (Lint & Type Check) #27319

Closed

Description

@github-actions

os-4-hourly-full-run-lint-type-check — 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 (Lint & Type Check)

Swept 2026-10-28T16:39:44.669Z · run log · commit d4427aedcf4c490637bdd40d850ce8344c4da4a1 · conclusion failure.
Lint & Type Check 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: 9dec05458f (run 40686729144, the last green Lint & Type Check schedule run) .. d4427aedcf — compare

Activity

  1. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    domain:devx#1 · sunhaolin · session_017xRBcVyH9FzSkzAGmz8LNE

    Claim: PM loop round 2 · 2026-10-28T17:45Z · main-red anchor (p0 at first touch; anchor exemption from the triage audit)
    Session: session_017xRBcVyH9FzSkzAGmz8LNE (devx seat 1)
    Account: sunhaolin (the seat's linked user as GET /user answers it; the card's assignee)
    Branch: none — no code is owed unless the re-run below fails again
    Worktree: none
    Domain: domain:devx
    Seat: domain:devx#1
    File surface: none yet. If the re-run reproduces, the root cause goes on its own card and this claim names it (stop on breach; explain in the report)
    Container & model: S, seat-run diagnosis, no dev · mode:subagent not used · model: default (opus) · effort: medium
    Clause-②: no
    Metadata-protocol: none
    Responsibility: no commit produces it. The failing step is actions/checkout in Lint · CI, release & engine gates (job 122942082788): git exit 128, RPC failed; HTTP 408, expected 'packfile' (check-run annotations). It is a fetch timeout before any gate ran. Every step after checkout is skipped, and Lint & Repo Gates is red only through its lane verdict | the platform path that covers it: the one re-run allowed for a job that died before any test body ran | it reaches main's full-battery signal only; it blocks nothing (card body)
    Thread-read: none
    Premise: holds (run 40723939011 on d4427aedcf, conclusion failure, read 2026-10-28T17:44Z)
    Serial constraints cleared: none touch this; no file is edited

    Stop-bleed: no commit in the range 9dec05458f..d4427aedcf is at fault, so there is nothing to revert. Action: ONE re-run of the failed jobs of run 40723939011, on the same d4427aedcf. Green ⇒ transient, and the card closes on that evidence. A second failure is real ⇒ root-cause card, with this anchor kept open. Related evidence: #22034 (slow full-depth checkouts) is on hold; this run is a lint lane on main, not its Test Core restart trigger, so it is cited there only if the re-run reproduces.

  2. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    domain:devx#1 · sunhaolin · session_017xRBcVyH9FzSkzAGmz8LNE

    Closed completed: the red was transient · 2026-10-28T18:12Z · claim 6476354289 fulfilled.

    Probe Reading
    Attempt 1 (scheduled, d4427aedcf) Lint · CI, release & engine gates failed at its Checkout repository step: git exit 128, RPC failed; HTTP 408, expected 'packfile'. Every gate step after it was skipped. Lint & Repo Gates was red only through that lane's verdict.
    Attempt 2 (the one re-run of the failed jobs, same d4427aedcf) Lint · CI, release & engine gates (job 122994805236) success. Lint & Repo Gates (job 122997966624) success. Run 40723939011 conclusion success, completed 2026-10-28T17:52Z.

    No commit in 9dec05458f..d4427aedcf was at fault, nothing was reverted, and no root-cause card is owed. The fetch timeout belongs to the checkout-cost class on #22034 (pm:on-hold). Its restart trigger names a Test Core shard on a product PR, not a lint lane on main, so that card is not woken. If the next 4-hourly run is red, the workflow reopens this card or files a fresh one.

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdomain:devxpriority:p0Critical: blocker, must ship before MVP

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions