ta
TanStack
GitHub
devtools
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
fix/stabilize-devtools-component-test-timeouts
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
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 run-many --target=test:e2e --parallel=1 --projects=devtools-e2e-react-vite,devtools-e2e-react-start,devtools-e2e-react-cloudflare,devtools-e2e-react-nitro,devtools-e2e-solid,devtools-e2e-vue,devtools-e2e-preact,devtools-e2e-angular
⌘K
Succeeded
nx run-many --target=test:e2e --parallel=1 --projects=devtools-e2e-react-vite,devtools-e2e-react-start,devtools-e2e-react-cloudflare,devtools-e2e-react-nitro,devtools-e2e-solid,devtools-e2e-vue,devtools-e2e-preact,devtools-e2e-angular
Click to copy
Linux
4 CPU cores
772d3ada
478
Get faster results
Learn how to enable distribution.
Atomizer enabled
8 groups of tasks optimized.
GitHub
devtools
Workspace