TanStackOSS
    devtools
    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.
    nx affected --targets=test:eslint,test:sherif,test:knip,test:lib,test:types,test:build,build
Succeeded
CI Pipeline Execution

nx affected --targets=test:eslint,test:sherif,test:knip,test:lib,test:types,test:build,build

Click to copy
Linux
4 CPU cores
read-write access token used
772d3ada478
100%

Cache hits

81 of 81 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

34 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools