Repository navigation
hourly full run: red on main (CI) #21909
Description
Activity
Path: fleet decision — the hourly full run says whether the whole tree is green (#16467) | 缺项 | none
Triage: routed —
pm:on-hold. An infrastructure fault: the runner was shut down mid-job, and seven jobs were cancelled before any test ran (bug·priority:p1·domain:devxstay as the generator filed them)Restart-when: the next scheduled
CIrun onmainaftercab6396715concludes. If it is green, this card closes as its generator says. If it is red on a named test, triage re-reads it.Triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-05T21:56Z. ⛔ Not a claim, ⛔ not a dispatch.Triage: lands in no repository file (GitHub-hosted runner capacity) ⇒
domain:devxkept; rationale: no test body failed in run37373300988.What the run shows:
Dogfood Regression Gate (3/3)ended withThe runner has received a shutdown signaland thenThe operation was canceled. Its last test file before that passed.- Seven jobs (
Build Core,Console Pin Gate,Test Core3/6, 4/6 and 5/6, andDogfood Regression Gate1/3) were cancelled after waiting about 15 minutes, with no runner assigned. Test CoreandDogfood Regression Gatethen failed only at their verify-shard-results steps, because shards were missing.- The range is empty (
cab6396715..cab6396715), and the same tree was green an hour earlier.
The same window on the relay: in that window, fleet-write runs on this repository queued for up to 10 minutes. Four
pr_createdispatches for objectui#11660 ended with "not acquired by Runner of type hosted". At this reading, nothing is queued and 14 runs are in progress, so the shortage has passed.⛔ No code change and no dispatch. Per the generator, the remedy is never to narrow or skip a check.
Generated by Claude Code
Closed by the triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-05T22:51Z, on the hold'sRestart-when:(6003871210): the next scheduledCIrun onmainaftercab6396715concluded green.- Run
37379700232atcab6396715, the same tree as both reds, concludedsuccess. - Both reds on this card were infrastructure:
- Run
37367118391(the one that filed it) had every non-green jobcancelledwith no runner assigned. - In run
37373300988, a runner was shut down mid-job and seven jobs were cancelled before any test ran. - No test body failed in either run. In
37373300988thefailureconclusion came only from the verify-shard-results steps finding shards missing.
- Run
- ⛔ No check was narrowed or skipped. If a later hourly run is red on a named test, the generator files it fresh. A closed card is never reopened.
Generated by Claude Code
- Run
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-05T21:25:54.910Z · run log · commit
cab639671528ef6f3a201e8995794378a4a28bfe· 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
cab6396715(run 37360596985, the last greenCIschedule run) ..cab6396715this 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