Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
35441
89bc4ed0 chore(repo): fix indentation of resolveTraceOut helper in unit-test-setup
by Craigory C...
Failed
35441
Fix available→
affb54f0 chore(repo): log jest cwd/argv at setup so we can verify config scoping The fs-trace shows that during nx:test the runtime is loading spec files from packages/nuxt and packages/web — i.e. jest is running tests outside packages/nx. Add a one-shot startup dump (cwd, argv, NX_* env, current jest test path) to dist/test-fs-trace/nx.startup.log so the next CI run reveals which config jest actually picks up and whether the inferred target's `cwd: packages/nx` is being honored.
by Craigory C...
Failed
35441
Generating fix→
ad6f4415 chore(repo): default fs-trace on so CI captures data without env wiring Inverts the gate to opt-out (NX_FS_TRACE_FOREIGN_READS=0 disables) so the diagnostic runs unconditionally on the next CI build regardless of whether the target's `env` config reaches the test process.
by Craigory C...
Canceled
35441
ad6f4415 chore(repo): default fs-trace on so CI captures data without env wiring Inverts the gate to opt-out (NX_FS_TRACE_FOREIGN_READS=0 disables) so the diagnostic runs unconditionally on the next CI build regardless of whether the target's `env` config reaches the test process.
by Craigory C...
Succeeded
35441
c00e8a31 chore(repo): guard native expandOutputs/getFilesForOutputsBatch from realRoot scans The `workspace-context` mock catches calls that go through `setupWorkspaceContext` / `getAllFileDataInContext`, but `tasks-runner/cache.ts` calls the native `expandOutputs(workspaceRoot, outputs)` directly — which drives `nx_walker` and walks every plugin's sources, surfacing as the same cross-project sandbox violation set. Same applies to `getFilesForOutputsBatch`. Wrap both functions to short-circuit to an empty result when the first arg is the real workspace root. TempFs callers continue to hit the real native implementation.
by Craigory C...
Failed
35441
Environment issue→
9035419a chore(repo): resolve workspace-context mock lazily so it works under jest's loader The previous mock captured `actual = jest.requireActual(workspaceContextPath)` in the factory closure, but jest's module loader returns the *in-progress* `module.exports` (still empty) when `requireActual` re-enters the same module from inside a `doMock` factory. That left every wrapped function as `undefined`, surfacing as "fn is not a function" the moment any test reached a workspace-context call (e.g. the `calculateHashesForCreateNodes` path that generator tests hit through `createNodes`). Resolve `actual` lazily — `jest.requireActual(...)[name](...)` per call — so the loader has finished evaluating the module by the time we look up the function. Also resolve the mocked path to a concrete file (`.ts` for the source, `index.js` for the napi binding) so the mock's key matches what callers' module resolution produces; an extension-less path didn't match the resolved `.ts` import id, leaving callers unmocked outside the nx package.
by Craigory C...
Failed
35441
4f67dcc4 chore(repo): mock workspace-context to skip real workspace scans in unit tests `--detectOpenHandles` (set globally in nx.json for the `test` target) makes jest run in-band, so the parent jest process is the test runner. The custom resolver's `argv`-based gate that points `NX_WORKSPACE_ROOT_PATH` at `tmp/unit` only matches `jest-worker`, never the in-band parent — which left the imported `workspaceRoot` constant frozen to the real CI workspace. The release suites (`release-graph`, `release-group-processor`, `multiple-release-groups`, `release-version`) call `createProjectFileMapUsingProjectGraph(...)` from `test-utils.ts`, which reads the global `workspaceRoot` and then constructs a native `WorkspaceContext` at it. The rust walker recursively scans every plugin's sources, generators, migrations, and templates — surfacing as ~4400 cross-project sandbox violations on `nx:test`. Add a `workspace-context` mock that short-circuits to safe empty defaults when handed the real workspace root, and a final-line `WorkspaceContext` constructor guard that throws if anything bypasses the higher-level mock. Tests using `TempFs` continue to pass through unchanged. The mocks use plain functions (not `jest.fn`) so suites calling `jest.resetAllMocks()` can't wipe them. Drop `virtual: true` from `project-graph.spec.ts`'s workspace-context mock so it correctly overrides the global setupFiles mock (the virtual flag keys by literal specifier, leaving the resolved-path mock unshadowed).
by Craigory C...
Succeeded
35441
fcd13cc2 chore(repo): mock graph + isolation by absolute path so CI hits the mock The previous mocks were keyed by the `nx/src/...` specifier, which the custom jest resolver routes through `node_modules/nx`. In a pnpm workspace `node_modules/nx` is a symlink to `packages/nx`, but jest does not realpath the resolved path, so this is a *different* module id than the one relative imports inside `packages/nx` resolve to (the direct `packages/nx/src/...` path). Locally the mock happened to apply because of how my paths normalized; in CI it didn't apply at all, the real graph ran, plugin workers spawned, and the cross-project violation count stayed flat at ~4500. Resolve the source files to their absolute physical paths via `__dirname` and mock those instead. Both resolution chains (`nx/src/...` and `./...`) end up at the same registry entry. The local-only `jest.unmock('./project-graph')` opt-out in `project-graph.spec.ts` continues to work because its relative resolution also lands at the same absolute path.
by Craigory C...
Canceled
35441
93de87ce chore(repo): scope unit-test plugin-isolation guard to real workspace The previous attempt set NX_WORKSPACE_ROOT_PATH unconditionally and mocked loadIsolatedNxPlugin to throw on every call. Both were too broad: - Pinning NX_WORKSPACE_ROOT_PATH to `tmp/unit` for all jest invocations changed the value of `workspaceRoot` that many tests had asserted on, breaking suites that relied on the real walk-up behavior. Restore the original conditional gate in `scripts/patched-jest-resolver.js`. - Mocking `loadIsolatedNxPlugin` to throw also blocked legitimate uses via TempFs (e.g. `getOnlyDefaultPlugins(tempFs.tempDir)` in `explicit-project-dependencies.spec.ts`). Make the guard inspect the `root` argument and only throw when it matches the real workspace root; pass through to the real implementation otherwise. Also opt out the one suite that exercises the real graph builder (`project-graph.spec.ts`) from the global `nx/src/project-graph/project-graph` mock via `jest.unmock`. Net effect: Fix 2 (graph mock) and the narrowed Fix 3 (smart isolation guard) remain. Full `packages/nx` jest suite matches the master baseline — no new failures.
by Craigory C...
Failed
35441
Fix available→
3093cd17 chore(repo): prevent unit tests from walking the real workspace The jest unit-test harness for packages/nx was computing the real project graph at test time — spawning plugin workers and scanning every plugin's sources/generators/templates — which surfaced as ~4500 cross-project sandbox violations on `nx:test`. Three layered fixes so a real workspace scan cannot happen and fails loudly if it does: 1. `scripts/patched-jest-resolver.js` now always points `NX_WORKSPACE_ROOT_PATH` at a throwaway `tmp/unit` dir. The previous `argv`-based guard skipped this under common invocations (`maxWorkers: 1`, no `:test` suffix), letting `workspace-root.ts` freeze to the real repo root on first import. 2. `scripts/unit-test-setup.js` mocks `nx/src/project-graph/project-graph` to return empty graphs for `createProjectGraphAsync`, `createProjectGraphAndSourceMapsAsync`, and `buildProjectGraphAndSourceMapsWithoutDaemon`. Relative imports inside `packages/nx` (e.g. `'../../project-graph/project-graph'`) resolve to the same absolute path and pick up this mock too — the existing `@nx/devkit` mock could not catch them. 3. `scripts/unit-test-setup.js` adds a guard mock on `loadIsolatedNxPlugin`. If a test slips past the graph mocks and tries to spawn a plugin worker, it throws with an actionable message instead of silently scanning the monorepo. `workspace-root.spec.ts` directly tests the walk-up logic in `workspaceRootInner`, which now short-circuits on the always-set env var, so it scopes the var away in a `beforeAll`/`afterAll`.
by Craigory C...