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-09-21T16:14:43.046Z · run log · commit 0e658fbe9315b808ffc6100424d5079bdc4ece93 · 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: 0e658fbe93 (run 35616059292, the last green CI schedule run) .. 0e658fbe93
⚠️ Nothing landed in that range. The same tree was green an hour ago and is red now, so
this is a FLAKE, an infrastructure fault, or a suite that depends on wall-clock time or on
something outside the repository. ⛔ Do not go looking for the commit that broke it.
Filed by .github/workflows/scheduled-full-run-card.yml. Generated by Claude Code
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-09-21T16:14:43.046Z · run log · commit
0e658fbe9315b808ffc6100424d5079bdc4ece93· conclusionfailure.CIruns the FULL battery onmainevery hour (#16467). Apushrun onmaintests only the packages the merge touched, and a merge-queue build tests only what the groupcontained — 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:
⚠️ Nothing landed in that range. The same tree was green an hour ago and is red now, so
0e658fbe93(run 35616059292, the last greenCIschedule run) ..0e658fbe93this is a FLAKE, an infrastructure fault, or a suite that depends on wall-clock time or on
something outside the repository. ⛔ Do not go looking for the commit that broke it.
Filed by
.github/workflows/scheduled-full-run-card.yml. Generated by Claude Code