Skip to content

Conversation

rarmatei
Copy link
Collaborator

@rarmatei rarmatei commented Oct 8, 2025

…nd affected-graph

Split the following test suites into smaller, more focused tests:

  • ng-add tests (cypress v9/v10, eslint, generate workspace, multiple projects)
  • cypress tests (component testing for Angular and Next, e2e execution, app generation)
  • eslint linter tests (dependency checks, flat config, linting errors, module boundaries, root configs)
  • affected-graph tests (affected star, focus/exclude, html/json output, show projects, git integration)

Fixes CLOUD-3756

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

…nd affected-graph

Split the following test suites into smaller, more focused tests:
- ng-add tests (cypress v9/v10, eslint, generate workspace, multiple projects)
- cypress tests (component testing for Angular and Next, e2e execution, app generation)
- eslint linter tests (dependency checks, flat config, linting errors, module boundaries, root configs)
- affected-graph tests (affected star, focus/exclude, html/json output, show projects, git integration)
Copy link

vercel bot commented Oct 8, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
nx-dev Ready Ready Preview Oct 17, 2025 10:53pm

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

Copy link
Contributor

nx-cloud bot commented Oct 8, 2025

View your CI Pipeline Execution ↗ for commit e40e2c3

Command Status Duration Result
nx affected --targets=lint,test,test-kt,build,e... ❌ Failed 47m 26s View ↗
nx run-many -t check-imports check-commit check... ✅ Succeeded 3m 2s View ↗
nx-cloud record -- nx-cloud conformance:check ✅ Succeeded 3s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 3s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded <1s View ↗

☁️ Nx Cloud last updated this comment at 2025-10-17 23:12:27 UTC

Copy link

netlify bot commented Oct 8, 2025

Deploy Preview for nx-docs ready!

Name Link
🔨 Latest commit e40e2c3
🔍 Latest deploy log https://app.netlify.com/projects/nx-docs/deploys/68f2c04fdcc8cd00085ab6b2
😎 Deploy Preview https://deploy-preview-33012--nx-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

@rarmatei rarmatei marked this pull request as ready for review October 17, 2025 10:35
@rarmatei rarmatei requested a review from a team as a code owner October 17, 2025 10:35
@rarmatei rarmatei requested review from a team as code owners October 17, 2025 10:35
@rarmatei rarmatei requested a review from FrozenPandaz October 17, 2025 10:35
);
expect(runCLI(`run ${appName}:e2e`)).toContain('All specs passed!');
}
expect(await killPort(4200)).toBeTruthy();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The port being killed (4200) doesn't match the port configured for the Next.js app (3000). Consider updating line 36 to expect(await killPort(3000)).toBeTruthy(); to ensure the correct port is terminated after the test completes.

Suggested change
expect(await killPort(4200)).toBeTruthy();
expect(await killPort(3000)).toBeTruthy();

Spotted by Graphite Agent

Fix in Graphite


Is this helpful? React 👍 or 👎 to let us know.

@rarmatei rarmatei requested a review from vsavkin as a code owner October 17, 2025 15:45
nx-cloud[bot]

This comment was marked as outdated.

- e2e-ci**module-federation/misc-rspack-interoperability**
- e2e-ci**module-federation/dynamic-federation.webpack**
- e2e-ci**docker**
- e2e-ci**module-federation/misc-rspack-interoperability**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line is a duplicate of line 42. The same target 'e2e-cimodule-federation/misc-rspack-interoperability' is listed twice, which could cause confusion or unexpected behavior in the workflow execution.

Spotted by Graphite Agent

Fix in Graphite


Is this helpful? React 👍 or 👎 to let us know.

Copy link
Contributor

@nx-cloud nx-cloud bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nx Cloud has identified a possible root cause for your failed CI:

The failure is classified as 'environment_state' due to the following factors:

Environmental Indicators Present:

  • Network error: HTTP 404 Not Found from npm registry
  • External service failure: Local npm registry at localhost:4873 is missing the required package
  • Package manager failure: pnpm unable to fetch yargs-parser dependency

No Correlation with Code Changes:
The PR modifies .nx/workflows/dynamic-changesets.yaml to consolidate test targets from an explicit list to a wildcard pattern (e2e-ci**) and changes the cache bust value in nx.json from 6 to 12. These configuration changes control test execution parallelism and caching behavior but do not affect package resolution, dependency availability, or npm registry contents.

Failure Occurs During Test Setup:
The error happens during the workspace creation phase (pnpm dlx create-nx-workspace@22.0.0) before any test logic executes. The workspace setup process requires fetching yargs-parser as a transitive dependency of create-nx-workspace, but the local test registry does not have this package available.

Potentially Pre-existing Issue:
The similar task failures reference indicates this test also fails on the master branch, suggesting the environmental issue exists independently of this PR's changes.

No Direct Link to Changed Code:
The error does not reference any modified files, functions, or configuration that was changed in this PR. The workflow configuration changes would not cause a package to disappear from or fail to be available in the npm registry.

The local npm registry environment needs to be fixed to ensure all required packages, including yargs-parser, are properly available for test workspace creation.

A code change would likely not resolve this issue, so no action was taken.

Nx CloudView in Nx Cloud ↗


🎓 To learn more about Self Healing CI, please visit nx.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants