Run details

NxWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/nx-vitest-test-timeout
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

fix(core): raise the nx package vitest timeout to cover the graph recompute spec project-graph-incremental-recomputation.spec.ts times out at exactly 35000ms on CI on every run that actually executes it: three runs in a row clipped at 35,009 / 35,018 / 35,070ms. Measured with the limit raised, the slowest test needs 42.4s on CI hardware, and its neighbours land at 32s and 29s. Locally the same test swings between 7s and 23s depending on pool load, so a 35s ceiling is inside the spec's own variance once CI's roughly 5x slowdown is applied. Master rarely shows it because most commits do not touch packages/nx and nx:test is served from cache. Any branch that busts that cache runs the spec every push and hits the limit. The jest preset carried the same 35s before the vitest move, so this is not a transform regression; the spec has been close to the line for a while and only surfaces on branches that execute it repeatedly.

nx affected --targets=lint,oxlint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run,validate-example

Succeeded

read-write access token used

3f64e8fe36850

1%

Potential flaky tasks

8 of 734 tasks retried.

24%

Cache hits

175 of 734 tasks used cache.

97%

Distribution saved time

55m 04s instead of 34h 09m 13s.

Atomizer enabled

49 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

NxWorkspace