Repository navigation
hourly full run: red on main (CI) #21778
Description
Activity
Path: fleet decision — the hourly full run says whether the whole tree is green (#16467) | 缺项 | none
Triage: closed
not_planned. One test timed out once ond7fff21736; that commit and the three hourly runs after it are greenTriage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-05T02:12Z. ⛔ Not a claim, ⛔ not a dispatch.Triage: lands in
packages/rest/src/meta-state-route-engine-outage.test.ts(test-only) ⇒domain:devx; rationale: nothing onmainis failing now, and a test-hardening change has no unlock target.Read now:
- The red run, 37235606957, failed in
Test Core (5/6)on one test: the multi-kernel wiring case atmeta-state-route-engine-outage.test.ts:296, which timed out at vitest's default 5000 ms. The other 4,896 tests in that package passed. - Four hourly runs are green since then: 37238364248 (2026-10-04T22:00Z, the same commit
d7fff21736), then 37242172109, 37245944574 and 37251396398. - So
mainhas no defect to fix. Hardening the test istoolingwith noUnblocks:target (triage-duties.mdline 34), and line 62 closes such a card at first touch.
Either condition brings it back:
- The same test times out again in an hourly run. The hourly run files a fresh card, and triage grades it as a recurring timing defect: p2,
domain:devx. - It fails on a PR or merge-queue run and holds up a landing. The card then carries
Unblocks:that PR.
Generated by Claude Code
- The red run, 37235606957, failed in
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-04T21:50:58.752Z · run log · commit
d7fff21736a7956bc753efb8a475e24276ea26e1· 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:
c9c555ac99(run 37232896045, the last greenCIschedule run) ..d7fff21736— compared7fff21736fix(cloud-connection): install-local purge deletes seed rows through the engine by their seed key (fix(cloud-connection): install-local purge deletes seed rows through the engine by their seed key #21773)Filed by
.github/workflows/scheduled-full-run-card.yml. Generated by Claude Code