Commit 92f69d0
authored
ci: stabilize flaky Test job (cap nx parallelism + raise vitest timeouts) (#478)
* test(devtools): raise vitest timeouts to stop flaky component test:lib in CI
The component tests added in #472 render the full Solid + goober tree and take
1-4s locally. Shared CI runners are ~4x slower (the suite runs in ~8s locally
but ~31s in CI), which pushes individual tests past vitest's default 5s
testTimeout and causes intermittent `@tanstack/devtools:test:lib` failures
across unrelated PRs (e.g. #471, #477).
Raise testTimeout and hookTimeout to 30s for the devtools package so slow CI
runs have headroom. Fast unit tests are unaffected; a real hang still fails
(just after 30s instead of 5s).
* ci: cap nx parallelism to 3 to fix flaky Test job
nx.json sets `parallel: 5`, which is fine for local dev machines but
oversubscribes GitHub-hosted runners: each affected `test:lib` (vitest) and
`test:types` (tsc) task spawns its own worker pool, so 5 heavy tasks at once
exhaust CPU/RAM and intermittently stall or OOM-kill deterministic tasks. That
produced flaky failures across unrelated PRs (#471, #477, #478) that pass on a
plain re-run.
The team already pins `test:e2e` to `--parallel=1` for the same reason; cap the
Test job's nx parallelism via NX_PARALLEL=3 (CI-only, leaves local dev at 5).
Combined with the raised vitest timeouts, this keeps tasks within the runner's
budget.1 parent e026667 commit 92f69d0
2 files changed
Lines changed: 12 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
12 | 18 | | |
13 | 19 | | |
14 | 20 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
16 | 22 | | |
17 | 23 | | |
18 | 24 | | |
| |||
0 commit comments