Repository navigation
hourly full run: red on main (CI) #23007
Description
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-12T12:26:11.228Z · run log · commit 0ede0f8ab36780687113c2c5fbf4c6d04b3febcc · 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: 9432bac077 (run 38240128220, the last green CI schedule run) .. 0ede0f8ab3 — compare
3071d3e989fix(platform-objects): a host translation bundle for a platform key wins over the platform bundle in either boot order (fix(platform-objects): a host translation bundle for a platform key wins over the platform bundle in either boot order #23019)2acff873adchore(objectui): move the console pin to 9646e2ed2bf3 (objectui#12185, objectui#12183) (refactor(plugin-security,platform-objects,spec): retire the catalog seeders, the per-organization catalog machinery and the four catalog objects; Setup creation is an environment write undersingleand refused under a wall (ADR-0131 D2/D3/D5/D13) #15204 C9) (chore(objectui): move the console pin to 9646e2ed2bf3 (objectui#12185, objectui#12183) (#15204 C9) #23018)c7d60378f0feat(spec,cloud-connection,cli): the installModes manifest key and the install door's unmanaged mode (ADR-0131 D6, stage S2) (feat(spec,cloud-connection,cli): the installModes manifest key and the install door's unmanaged mode (ADR-0131 D6, stage S2) #22916)d294951133fix(plugin-audit, service-messaging): boot-time system-table provisioning honours OS_SKIP_SCHEMA_SYNC (fix(plugin-audit, service-messaging): boot-time system-table provisioning honours OS_SKIP_SCHEMA_SYNC #23021)5187e5700efix(docs): light the top nav on a blog post — fumadocs matches against the public path, not the /en prerender path (fix(docs): light the top nav on a blog post — fumadocs matches against the public path, not the /en prerender path #23028)5dda60023bci(lint): Lint & Repo Gates becomes an aggregate over eight parallel lanes; PM dispatch-gates runs its fast tier on PR and queue (ci(lint): measure whereLint & Repo Gates' 198 serial steps spend 14–37 minutes, and bring the maintainer a split plan (maintainer-directed) #22991) (ci(lint): Lint & Repo Gates becomes an aggregate over eight parallel lanes; PM dispatch-gates runs its fast tier on PR and queue (#22991) #23014)e4a770d6b6docs(governed): record the allowOrgOverride → allowEnvironmentOverlay rename in AGENTS.md rule 7, the objectstack-ai skill and the ADR-0005 / ADR-0010 headers (spec: renameallowOrgOverrideto an environment-overlay key with an ADR-0087 load-time conversion (ADR-0131 C5's spec half, split from #15206 per #22007 ruling C) #22340 S3) (docs(governed): record the allowOrgOverride → allowEnvironmentOverlay rename in AGENTS.md rule 7, the objectstack-ai skill and the ADR-0005 / ADR-0010 headers (#22340 S3) #23011)8f5354b0cfci: two-speed CI — PR and queue runs carry the fast set, the full battery runs on main and gates the publish lane, required set 7 → 5 (ci: two-speed CI — PR and queue runs carry the fast set, the full battery runs on main and gates the publish lane, required set 7 → 5 #23020)edecd44851test(showcase): the boot-splash wait sees both English lines and the data-boot-splash marker (test(showcase): the boot-splash wait sees both English lines and the data-boot-splash marker #23030)58f5c90999fix(metadata-core): a ^18 artifact built during the v18 prerelease boots on a later runtime — the door replays step 18 for a floor of 18.0.0 (fix(metadata-core): a ^18 artifact built during the v18 prerelease boots on a later runtime — the door replays step 18 for a floor of 18.0.0 #23023)0ede0f8ab3test(spec): the connector-author-shape compile test carries its own 180 s timeout (test(spec): the connector-author-shape compile test carries its own 180 s timeout #22969)
Filed by.github/workflows/scheduled-full-run-card.yml. Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 12, 2026
Reading ·
domain:devxseat 1 ·os-warren·session_012yK1ddAdAqfzwigRHZq3r2· 2026-10-12T10:18Z. ⛔ Not a claim, ⛔ no label change.74c4b3435e, 09:11Z) has one failing step,Test Core→ "Check the per-package suite-duration ceilings". It is the first hourly run on a tree carrying 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's ruled change (eede467f3), so a red here is aschedulered by design. Two packages are just over (annotations viascripts/pm/ci-failure.mjs):@objectstack/cloud-connection: 165.64s, over its 163.89s ceiling(1.01x);@objectstack/service-cluster-redis: 28.61s, over its 28.00s ceiling(1.02x, above the 20 s floor).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 rule ("two consecutive hourly reds on one package are a reading, one is not"):cloud-connectionwas over on 06:05Z (167.04 s) and 09:11Z, and within its ceiling on 07:25Z and 08:15Z, so it has not crossed twice in a row.service-cluster-rediscrosses for the first time here.111ffff556, which was stillin_progressat this comment.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 remedy is a ruled raise, or a faster suite, for that package.Generated by Claude Code
objectstack-fleet commentedon Oct 12, 2026
Second reading ·
domain:devxseat 1 · 2026-10-12T10:47Z. The 10:07Z hourly run38234348113(111ffff556) is red too:cloud-connection209.04 s (1.28x),service-analytics1.12x,plugin-approvals1.05x andclient1.01x.Test Core (6/6)drift is also red.That makes the second consecutive red on
cloud-connection, which #22949's ruling counts as a reading. The reading and the mechanism (this hourly run executed the whole workspace after ten PRs landed in the hour) are on #22949,6122739059. The remedy is the maintainer's call. This card stays open until a ruled change lands, or an hourly run is green.Generated by Claude Code
objectstack-fleet commentedon Oct 12, 2026
Closed by the director seat on #22949's ruling E (the newest
Ruling:comment there; the maintainer's word verbatim 「22949 同意」), 2026-10-12T14:22Z: the hourly reds this card tracks are the timing gate's reading of runner load on busy hours, not a package regression (client,cloud-connection,service-analytics,runtimecross the same near-ceiling lines whatever their code does). The remedy is E1 (both timing steps report-only on every event) and E2 (the refresh diff files cards), both filed in this act; the hourly run goes green at the first schedule after E1 lands. ⛔ Not a claim.