Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
36825
55d1656f fix(core): stop the output specs depending on a fetched snapshot bundle getTaskOutputs and getExpandedTaskInputs both call loadIoSnapshotsForHead, which reads a bundle off disk. Neither spec mocked it, so the snapshot branch was skipped locally, where no bundle exists, and taken on CI, where Nx Cloud has fetched one. Taking it reached customHasherTaskIds, whose call to readProjectsConfigurationFromProjectGraph the project-graph mock does not provide, and 5 tests across the two files failed. Pin the bundle absent so the result no longer depends on ambient cache state. Confirmed by forcing the bundle present locally, which reproduces the CI failure exactly.
by Craigory C...
Failed
36825
c3efcb05 test(core): cover includeIgnored affected filesets
by Craigory C...
Failed
36825
d191117d cleanup(core): move the affected touched-project locators into rust Ports getTouchedProjects, getImplicitlyTouchedProjects and getTouchedProjectsFromProjectGlobChanges to a native locateTouchedProjects. No behavior change: the existing affected specs pass untouched. The lockfile, npm-package and tsconfig locators stay in TypeScript because they depend on the npm/yarn/pnpm/bun lockfile parsers. They are passed across the boundary as ThreadsafeFunction callbacks and invoked once per run, so the locator set stays extensible from JS. Graph pruning stays in TypeScript too: the native ProjectGraph models dependencies as HashMap<String, Vec<String>>, with no edge type or source, so it cannot rebuild what filterAffected returns. Also deletes workspace-json-changes.ts, the angular.json locator that was already unregistered and had no remaining referents.
by Craigory C...
Failed
36825
9f620517 cleanup(core): move the affected touched-project locators into rust Ports getTouchedProjects, getImplicitlyTouchedProjects and getTouchedProjectsFromProjectGlobChanges to a native locateTouchedProjects. No behavior change: the existing affected specs pass untouched. The lockfile, npm-package and tsconfig locators stay in TypeScript because they depend on the npm/yarn/pnpm/bun lockfile parsers. They are passed across the boundary as ThreadsafeFunction callbacks and invoked once per run, so the locator set stays extensible from JS. Graph pruning stays in TypeScript too: the native ProjectGraph models dependencies as HashMap<String, Vec<String>>, with no edge type or source, so it cannot rebuild what filterAffected returns. Also deletes workspace-json-changes.ts, the angular.json locator that was already unregistered and had no remaining referents.
by Craigory C...