From c693198caa01e04bebbf60e2033dfbd4db1cfa64 Mon Sep 17 00:00:00 2001 From: Willow Sparks Date: Tue, 10 Nov 2026 09:27:42 +0000 Subject: [PATCH] ci: run four workspace slots, not eight Eight whole-binary slots on the shared runner over-subscribed it: the context and catalog-stream latency targets stretched to 250-270 s, and the 60 s harness deadlines behind them began timing out run after run, each time in a different target. Four keeps the tail bounded while the package job builds alongside. --- .forgejo/workflows/ci.yml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.forgejo/workflows/ci.yml b/.forgejo/workflows/ci.yml index 25d6e4cc7..683438ae0 100644 --- a/.forgejo/workflows/ci.yml +++ b/.forgejo/workflows/ci.yml @@ -22,9 +22,11 @@ env: CARGO_INCREMENTAL: "0" CARGO_PROFILE_DEV_DEBUG: "0" CARGO_PROFILE_TEST_DEBUG: "0" - # The workspace scheduler owns whole-binary slots. Eight fills the 32-core - # runner without making every harness fight for a CPU. - PA_WORKSPACE_TEST_SLOTS: "8" + # The workspace scheduler owns whole-binary slots. Eight over-subscribed the + # runner: timing-sensitive targets stretched to 250-270 s and their 60 s + # harness deadlines started timing out. Four bounds the tail while the package + # job builds alongside. + PA_WORKSPACE_TEST_SLOTS: "4" jobs: # Lint stays a cheap gate. The heavy package and workspace jobs start -- knotmirror 0.0.1