Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36339
b6160b26 fix(vitest): align atomized spec discovery with Vitest's config resolution The glob-based atomized test discovery resolved specs differently from how Vitest resolves them at run time, so the `${ciTargetName}--*` targets could enumerate the wrong spec set with no warning. Two divergences: - The serve config was resolved under Vite `mode: 'development'`, but Vitest runs under `mode: 'test'`. A config that branches `test.include`/`exclude` on `mode` enumerated a different set during graph creation than at test time. Resolve under `mode: 'test'` to match. - `test.includeSource` was globbed even under `typecheck.enabled` + `typecheck.only`, where Vitest collects only type tests and skips in-source files. Gate the includeSource glob with the same `typecheck.only` guard the regular include already uses. The e2e exercises the mode branch via a config that keys `test.include` on `mode`; a unit test covers the typecheck.only + includeSource combination.
by Leosvel Pé...
Failed
36339
Flaky task→
b6160b26 fix(vitest): align atomized spec discovery with Vitest's config resolution The glob-based atomized test discovery resolved specs differently from how Vitest resolves them at run time, so the `${ciTargetName}--*` targets could enumerate the wrong spec set with no warning. Two divergences: - The serve config was resolved under Vite `mode: 'development'`, but Vitest runs under `mode: 'test'`. A config that branches `test.include`/`exclude` on `mode` enumerated a different set during graph creation than at test time. Resolve under `mode: 'test'` to match. - `test.includeSource` was globbed even under `typecheck.enabled` + `typecheck.only`, where Vitest collects only type tests and skips in-source files. Gate the includeSource glob with the same `typecheck.only` guard the regular include already uses. The e2e exercises the mode branch via a config that keys `test.include` on `mode`; a unit test covers the typecheck.only + includeSource combination.
by Leosvel Pé...
Succeeded
36339
c6ba43c4 cleanup(vitest): read normalized options.command in the atomized e2e assertion The e2e reading `details.targets[t].command` from `nx show project --json` always saw `undefined`: Nx's run-commands syntactic sugar moves a target's top-level `command` into `options.command` before it reaches the project graph, and the JSON serializes the normalized graph. Read `options.command` so the equality assertion matches the value the atomized targets actually carry.
by Leosvel Pé...
Canceled
36339
c6ba43c4 cleanup(vitest): read normalized options.command in the atomized e2e assertion The e2e reading `details.targets[t].command` from `nx show project --json` always saw `undefined`: Nx's run-commands syntactic sugar moves a target's top-level `command` into `options.command` before it reaches the project graph, and the JSON serializes the normalized graph. Read `options.command` so the equality assertion matches the value the atomized targets actually carry.
by Leosvel Pé...
Failed
36339
Fix ready→
296eb01b fix(vitest): discover atomized tests using Vitest's serve-mode config Atomized test discovery read the build-resolved Vite config, but Vitest runs its tests through a Vite server in serve mode. Plugins gated to `apply: 'serve'` and any command-sensitive `test` include/exclude are absent from the build resolution, so the glob path could enumerate a different set of spec files than `vitest run` executes, silently producing a wrong atomized target list. Resolve the config in serve mode for glob discovery and runtime-fallback detection, keeping the build resolution for outputs. The serve resolution is skipped when the Vitest runtime is forced, since that path resolves its own config. Read in-source test candidates in bounded batches so a large candidate set cannot exhaust file descriptors, and cover the `typecheck.only` and batch-boundary discovery branches with unit tests.
by Leosvel Pé...
Failed
36339
ae676acc fix(vitest): discover atomized tests using Vitest's serve-mode config Atomized test discovery read the build-resolved Vite config, but Vitest runs its tests through a Vite server in serve mode. Plugins gated to `apply: 'serve'` and any command-sensitive `test` include/exclude are absent from the build resolution, so the glob path could enumerate a different set of spec files than `vitest run` executes, silently producing a wrong atomized target list. Resolve the config in serve mode for glob discovery and runtime-fallback detection, keeping the build resolution for outputs. The serve resolution is skipped when the Vitest runtime is forced, since that path resolves its own config. Read in-source test candidates in bounded batches so a large candidate set cannot exhaust file descriptors, and cover the `typecheck.only` and batch-boundary discovery branches with unit tests.
by Leosvel Pé...