Repository navigation
hourly full run: red on main (CI) #21916
Description
Activity
Path: fleet decision — the hourly full run says whether the whole tree is green (#16467) | 缺项 | none
Triage: routed —
pm:on-hold. The red is the third timeout of one test, and that test now has its own card: #21920 (bug·priority:p1·domain:devxstay as the generator filed them)Restart-when: the next scheduled
CIrun onmainaftere6dc7a2406concludes. If it is green, this card closes, and the timing work stays on #21920. If it is red on the same case withTest timed out, this card closes against #21920, which already owns that case. If it is red on anything else, triage re-reads it.Triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-05T23:56Z. ⛔ Not a claim, ⛔ not a dispatch.Triage: lands in
packages/rest/src/meta-state-route-engine-outage.test.ts(:296) ⇒ the work is on #21920 indomain:cli; rationale: this card is the generator's signal, and a work card must not have its body rewritten on the next red.What the run shows (run
37386040871, ate6dc7a2406):Test Core (5/6)had one failure: the[#15405] §0multi-kernel wiring case,Test timed out in 5000ms. The other 4,897 tests in@objectstack/restpassed.- The range holds one commit, fix(metadata-core,rest,runtime): judge an objectOverride action param against the object it names #21904 (
objectOverrideaction params). Itsrest-server.tschange is on the object-schema mask path, not the state route this case drives. The same case timed out the same way on hourly full run: red on main (CI) #21757 and hourly full run: red on main (CI) #21778, before that commit existed, so the commit is not the reading here.
This amends my close of #21778. That was the second timeout of this same case, and #21757's
Restart-when:already said a repeat becomes the test's timing card. I closed itnot_plannedinstead. #21920 is that card, filed now with all three occurrences.
Generated by Claude Code
Closed by the triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-06T00:58Z, on the hold'sRestart-when:(6005911233): the next scheduledCIrun onmainaftere6dc7a2406concluded green.- Run
37391844594at833d57c9cf, which containse6dc7a2406, concludedsuccess. - The red's only failure was the third
Test timed out in 5000msofmeta-state-route-engine-outage.test.ts:296. That case's timing is owned by test(rest):meta-state-route-engine-outage.test.ts's multi-kernel wiring case times out at vitest's 5000 ms default under the hourly full run, and has turnedmain's hourly run red three times in two days #21920 (domain:cli, nowpm:dispatched), which keeps all three occurrences. This green run does not close it. - ⛔ No check was narrowed or skipped. If a later hourly run times out on the same case, it belongs to test(rest):
meta-state-route-engine-outage.test.ts's multi-kernel wiring case times out at vitest's 5000 ms default under the hourly full run, and has turnedmain's hourly run red three times in two days #21920. Anything else, the generator files fresh.
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-05T23:15:19.049Z · run log · commit
e6dc7a240617eaeef9a64e788bf6e5561c107f1b· 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:
cab6396715(run 37379700232, the last greenCIschedule run) ..e6dc7a2406— comparee6dc7a2406fix(metadata-core,rest,runtime): judge an objectOverride action param against the object it names (fix(metadata-core,rest,runtime): judge an objectOverride action param against the object it names #21904)Filed by
.github/workflows/scheduled-full-run-card.yml. Generated by Claude Code