Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running affected:test in parallel shows karma errors #606

Closed
Nxt3 opened this issue Jun 25, 2018 · 5 comments
Closed

Running affected:test in parallel shows karma errors #606

Nxt3 opened this issue Jun 25, 2018 · 5 comments

Comments

@Nxt3
Copy link

Nxt3 commented Jun 25, 2018

I get the following error when running yarn affected:test --parallel --all:

 30% building modules 170/171 modules 1 active …ary-nav/secondary-nav-item.component.js25 06 2018 10:33:17.737:ERROR [karma]: { Error: listen EADDRINUSE 0.0.0.0:9876
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at Server.setupListenHandle [as _listen2] (net.js:1351:14)
    at listenInCluster (net.js:1392:12)
    at doListen (net.js:1501:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '0.0.0.0',
  port: 9876 }

This happens for each test. It's not failing tests--but it's shown in the output and I'd like to fix it if possible.

Running sequentially is fine.

@Nxt3
Copy link
Author

Nxt3 commented Jun 25, 2018

I run ps aux | grep node and don't see anything other than the grep call I run listed.

@FrozenPandaz
Copy link
Collaborator

FrozenPandaz commented Jun 27, 2018

The issue is the same port is used for every project. Either we need to identify unused ports during code generation or utilize a library which can find open ports.

@Nxt3
Copy link
Author

Nxt3 commented Jun 28, 2018

Me thinks it's a karma issue: karma-runner/karma#3065

@FrozenPandaz
Copy link
Collaborator

@Nxt3 It appears that karma issue has been fixed. And with #783 Nx workspaces will use karma@~3.0.0 and has the fix and this does not seem to happen anymore :)

@github-actions
Copy link

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants