Open ghost opened 2 months ago
@danr-za I'm investigating this. I just want to clarify if you are using Nx Agents, or if this is running directly on GitHub Actions?
Also, if you set NX_ISOLATE_PLUGINS=false
in CI, does that resolve the original issue?
This is the repo that I'm trying to reproduce this with, but without any success so far: https://github.com/jaysoo/issue27816
Thanks @jaysoo . We are running directly on GitHub without Nx Agents (yet, we need to upgrade)
This issue has been automatically marked as stale because no reproduction was provided within 7 days. Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue. Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues. This issue will be closed in 21 days if a reproduction is not provided. If a reproduction has been provided, please reply to keep it active. Thanks for being a part of the Nx community! 🙏
Not stale. @jaysoo could you add me as a collaborator to that repo? I'll try to play with it around. I see CI is set up
@danr-za Added you as a collaborator.
Current Behavior
We are using workspace code generators using
@nx/plugin
. Because we have updated prettier to v3 a while ago, we have switched to testing the generators withvitest
instead ofjest
as it introduced some ESM stuff. Lately, we have upgraded Nx from v19.0.0 to v19.6.4. During the upgrade, we noticed issues with those tests timing out or failing in CI, using Github actions. Most code generators use Nx generators under the hood (e.g.@nx/js:lib
,@nx/react:lib
, etc.) I have tried diagnosing the problem, and these are some interesting outputs:@nx/vite:vitest
TypeError: Cannot destructure property 'resolver' of 'pending.get(...)' as it is undefined. ❯ createNodesResult ../../node_modules/nx/src/project-graph/plugins/isolation/plugin-pool.js:162:25 ❯ consumeMessage ../../node_modules/nx/src/project-graph/plugins/isolation/messaging.js:38:32 ❯ ../../node_modules/nx/src/project-graph/plugins/isolation/plugin-pool.js:77:47 ❯ Socket. ../../node_modules/nx/src/utils/consume-messages-from-socket.js:13:17
testTimeout
to 50s, tests are passing again. This is interesting because with that same configuration, with the defaulttestTimeout,
in Nx 19.0.0 the tests did not timeout.Notes:
Expected Behavior
Either:
GitHub Repo
No response
Steps to Reproduce
@nx/plugin
vitest
libraryGenerator
from@nx/js
in your code generator, withformatFiles
too (not sure it has impact though)Generator:
Test:
Nx Report
Failure Logs
No response
Package Manager Version
4.4.1
Operating System
Additional Information
No response