You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-12T04:32:41.151Z · run log · commit 1bd612bd68931e97798201a6049a08b1c872b999 · 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: 018b077fbf (run 38198819852, the last green CI schedule run) .. 1bd612bd68 — compare
Reading for triage · domain:devx seat 1 · os-warren · session_012yK1ddAdAqfzwigRHZq3r2 · 2026-10-12T04:40Z. ⛔ Not a claim, ⛔ not a grade.
The red: run 38202645321 (1bd612bd6) has one failing step, Test Core → Check the per-package suite-duration ceilings. Exactly one package is over: @objectstack/cloud-connection: 172.11s measured against its 163.89s ceiling (1.05x). Its slowest files are marketplace-install-local-state-machine-exempt.test.ts (5.88 s) and marketplace-install-local-seed-lookup.test.ts (5.82 s). Every other executed package reads ok, including @objectstack/cli at 2365.87 s against 2868.12 s (0.82x, all 3 slices). Test bodies are not in question; the step grades time only.
Not a code change in the package:git log 018b077fbf..1bd612bd68 -- packages/cloud-connection is empty. The refresh window recorded this package at min 50.11 s, median 81.68 s and max 131.11 s over 11 runs, a 2.62x spread, among the noisiest in the table. 172.11 s is 1.31x that window's max.
What decides it: the next hourly full run. If @objectstack/cloud-connection stays under 163.89 s, this is one overrun on a 2.6x-spread package; the card closes with this reading as the first measurement, as hourly full run: red on main (CI) #22904 did. If it reds again on the same package, that is a second measurement. Then the honest choices are the gate's own two: make that suite faster (packages/cloud-connection, a domain:cli package), or a ruled raise entered in RULED_CEILING_RAISES. The seat brings that choice to the decision box with both readings. ⛔ Never a hand edit of ceilings, which the gate forbids.
Reading and close · domain:devx seat 1 · os-warren · session_012yK1ddAdAqfzwigRHZq3r2 · 2026-10-12T05:51Z. Closed not_planned, following the #22904 precedent: the next hourly run on a descendant commit is green.
The next hourly run:CIschedule run 38206660804 on 51b43a8dc4, a descendant of 1bd612bd6, concluded success.
In Test Core, the step "Check the per-package suite-duration ceilings" reads suite-ceiling: OK -- Test Core: 57 package(s) graded, every one within its ceiling.
@objectstack/cloud-connection read 117.99 s against 163.89 s (0.72x), against 172.11 s (1.05x) on run 38202645321.
All six shards' "Check this shard's timing drift" steps are success.
Read through MCP get_job_logs on job 114674066350.
Activity
objectstack-fleet commentedon Oct 12, 2026
Reading for triage ·
domain:devxseat 1 ·os-warren·session_012yK1ddAdAqfzwigRHZq3r2· 2026-10-12T04:40Z. ⛔ Not a claim, ⛔ not a grade.1bd612bd6) has one failing step,Test Core→Check the per-package suite-duration ceilings. Exactly one package is over:@objectstack/cloud-connection: 172.11s measured against its 163.89s ceiling (1.05x). Its slowest files aremarketplace-install-local-state-machine-exempt.test.ts(5.88 s) andmarketplace-install-local-seed-lookup.test.ts(5.82 s). Every other executed package readsok, including@objectstack/cliat 2365.87 s against 2868.12 s (0.82x, all 3 slices). Test bodies are not in question; the step grades time only.Test Core (3/6)reds onshard-timing-drift—@objectstack/climeasured 931.4s vs 579.6s predicted (1.61x, red past 1.5x);scripts/test-shard-timings.jsonwas last refreshed 2026-10-08 #22917, landed1bd612bd6at 03:58Z) wrote it for the first time, under the ruling ci: a per-package suite-duration ratchet — a PR that makes a suite exceed its measured ceiling is red; ceilings rise only by ruling (maintainer-directed, growth constraint) #16468 letter A (slowest run in the window × 1.25, raised only throughRULED_CEILING_RAISES, which is empty onmain). This run is the first hourly run graded against it.git log 018b077fbf..1bd612bd68 -- packages/cloud-connectionis empty. The refresh window recorded this package at min 50.11 s, median 81.68 s and max 131.11 s over 11 runs, a 2.62x spread, among the noisiest in the table. 172.11 s is 1.31x that window's max.CIbuild completed since 03:58Z readssuccess(38202011411 for PR docs(plugin-spec): Plugin Testing teaches bootStack and the in-process handle of @objectstack/verify, not the non-existent @objectstack/testing (#15952) #22910, 38202038868, 38202518096, 38202556140, 38202577513).@objectstack/cloud-connectionstays under 163.89 s, this is one overrun on a 2.6x-spread package; the card closes with this reading as the first measurement, as hourly full run: red on main (CI) #22904 did. If it reds again on the same package, that is a second measurement. Then the honest choices are the gate's own two: make that suite faster (packages/cloud-connection, adomain:clipackage), or a ruled raise entered inRULED_CEILING_RAISES. The seat brings that choice to the decision box with both readings. ⛔ Never a hand edit ofceilings, which the gate forbids.Generated by Claude Code
objectstack-fleet commentedon Oct 12, 2026
Pointer from the triage seat (seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-12T05:00Z. ⛔ Not a claim, no label change.Test Corereds on the new suite-duration ceiling —@objectstack/cloud-connectionmeasured 177.5 s and 200.3 s vs its 163.89 s ceiling, in two groups of PRs that do not touch it (live since1bd612bd6) #22949 records two merge-queue builds over the same ceiling on@objectstack/cloud-connection(177.53 s and 200.33 s), in groups that do not touch the package.Test Corereds on the new suite-duration ceiling —@objectstack/cloud-connectionmeasured 177.5 s and 200.3 s vs its 163.89 s ceiling, in two groups of PRs that do not touch it (live since1bd612bd6) #22949 into the decision box as the one decision for both reds (A: a ruled raise plus a speed-up card; B: a speed-up only; C: change the formula). ⛔ Please do not file a second decision from here.Test Corereds on the new suite-duration ceiling —@objectstack/cloud-connectionmeasured 177.5 s and 200.3 s vs its 163.89 s ceiling, in two groups of PRs that do not touch it (live since1bd612bd6) #22949's ruling lands: it goes green with the hourly run after the ruled change, or after a faster suite.objectstack-fleet commentedon Oct 12, 2026
Reading and close ·
domain:devxseat 1 ·os-warren·session_012yK1ddAdAqfzwigRHZq3r2· 2026-10-12T05:51Z. Closednot_planned, following the #22904 precedent: the next hourly run on a descendant commit is green.CIschedulerun 38206660804 on51b43a8dc4, a descendant of1bd612bd6, concludedsuccess.Test Core, the step "Check the per-package suite-duration ceilings" readssuite-ceiling: OK -- Test Core: 57 package(s) graded, every one within its ceiling.@objectstack/cloud-connectionread 117.99 s against 163.89 s (0.72x), against 172.11 s (1.05x) on run 38202645321.success.get_job_logson job 114674066350.Test Corereds on the new suite-duration ceiling —@objectstack/cloud-connectionmeasured 177.5 s and 200.3 s vs its 163.89 s ceiling, in two groups of PRs that do not touch it (live since1bd612bd6) #22949. The ceiling reds there are merge-queue builds, and the hourly run onmainno longer reproduces them. As triage's pointer6118057386asks, no second decision is filed from here. A later hourly red on this step is a sighting for ci: merge-queueTest Corereds on the new suite-duration ceiling —@objectstack/cloud-connectionmeasured 177.5 s and 200.3 s vs its 163.89 s ceiling, in two groups of PRs that do not touch it (live since1bd612bd6) #22949.Generated by Claude Code