Skip to content

Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS

ci: give Windows validation measured deadline headroom

[._.]/ Adam Eivy4dc1439cece5
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index ace591e731..bbed3ff1e2 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -1131,8 +1131,11 @@ jobs:
id: windows-tests
# A step timeout FAILS the step (log kept, `if: failure()` reporting
# runs); the job-level timeout would cancel the job and lose the log
- # (#10415). Observed healthy runs take 2-10 minutes.
- timeout-minutes: 15
+ # (#10415). Full Windows shards now approach/exceed 15 minutes: one
+ # completed 19,911 tests in 877.6s before post-test timeout; another
+ # reached 1,091/1,100 modules at the deadline (2026-10-24, #13402).
+ # Keep headroom within the unchanged 40-minute job and two-worker cap.
+ timeout-minutes: 20
env:
PORTOS_TEST_MEMO_DIR: ${{ runner.temp }}/portos-test-memo
# Outside the launcher's disposable temp root; recoverable after exit.
diff --git a/docs/GITHUB_ACTIONS.md b/docs/GITHUB_ACTIONS.md
index 38fa111e79..4aafbee0b4 100644
--- a/docs/GITHUB_ACTIONS.md
+++ b/docs/GITHUB_ACTIONS.md
@@ -754,13 +754,18 @@ The three test-runner jobs are therefore matrices. The impact job emits
`server_shards`, `client_shards`, and `windows_shards` — `[1]` for exact-file
plans and `[1..n]` for full plans. Windows also uses its full matrix for
related-test plans: a single shared source can select most of the server graph
-and exceed the 15-minute test-step budget on one Windows runner. Matrices are
+and exceed the bounded test-step budget on one Windows runner. Full Windows
+shards reached 19,911 passing tests in 877.6 seconds before post-test timeout,
+and another reached 1,091/1,100 modules at the 15-minute deadline (2026-10-24,
+#13402). The test step now has 20 minutes within its unchanged 40-minute job;
+the two-worker cap, matrix size and all tests remain unchanged. Matrices are
sized by `FULL_SUITE_SHARDS` in
`scripts/ci-test-plan.js` (client 3, Windows 3, server 2) — and each job builds
its matrix from that output. The decision has to be made in the planner: a
job-level `if` cannot read the `matrix` context, so a job cannot skip its own
extra shards. `scripts/run-ci-tests.js` turns `CI_SHARD=<index>/<count>` into
-Vitest's `--shard`, which slices the file list by path hash — every shard is a
+a file-selection slice before launching Vitest (without a `--shard` flag),
+using the same path-hash partition — every shard is a
fixed, disjoint subset, and their union is the complete selected suite. Windows
related plans retain the same source graph and explicit contracts on every
shard; only execution is partitioned. Scoped Linux plans fan out the same way