Conversation
|
View your CI Pipeline Execution ↗ for commit 963bf9d
☁️ Nx Cloud last updated this comment at |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud is proposing a fix for your failed CI:
We fixed the should run oxlint successfully e2e test by setting NX_NO_CLOUD: 'true' in the env passed to execSync. The test workspace is created with --nxCloud=skip, but the CI NX_CLOUD_ACCESS_TOKEN leaks in via process.env, causing Nx Cloud to reject the task run because the token doesn't belong to the ephemeral test workspace. Scoping the cloud opt-out to just this call prevents Nx Cloud from intercepting the lint task without affecting the rest of the test setup.
Tip
✅ We verified this fix by re-running oxlint-e2e:e2e.
diff --git a/e2e/oxlint-e2e/src/oxlint.spec.ts b/e2e/oxlint-e2e/src/oxlint.spec.ts
index ca4337b..755b142 100644
--- a/e2e/oxlint-e2e/src/oxlint.spec.ts
+++ b/e2e/oxlint-e2e/src/oxlint.spec.ts
@@ -66,7 +66,7 @@ describe('oxlint plugin', () => {
execSync('yarn nx run lib-a:lint', {
cwd: projectDirectory,
stdio: 'inherit',
- env: process.env,
+ env: { ...process.env, NX_NO_CLOUD: 'true' },
});
});
});
Or Apply changes locally with:
npx nx-cloud apply-locally e5m1-Pg8A
Apply fix locally with your editor ↗ View interactive diff ↗
🎓 Learn more about Self-Healing CI on nx.dev
|
Hi! I was wondering if there's a plan to get this PR merged in the next few days? |
@juristr hi friendly follow-up here :) |
|
@andres-ito1 looking into it. just got swamped with other work |
2 participants
No description provided.