Skip to content
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.

"EADDRINUSE" error during smoke tests #1511

Closed
artem-zakharchenko opened this issue Sep 24, 2019 · 2 comments
Closed

"EADDRINUSE" error during smoke tests #1511

artem-zakharchenko opened this issue Sep 24, 2019 · 2 comments

Comments

@artem-zakharchenko
Copy link
Contributor

Describe the bug
During the current Dredd's smoke tests there is an EADDRINUSE exception being thrown when trying to run dredd-example:

Listening on port 3000
events.js:186
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::3000
    at Server.setupListenHandle [as _listen2] (net.js:1298:14)
    at listenInCluster (net.js:1346:12)
    at Server.listen (net.js:1434:7)
    at Function.listen (/home/circleci/project/dredd-example/node_modules/express/lib/application.js:618:24)
    at Object.<anonymous> (/home/circleci/project/dredd-example/app.js:216:5)
    at Module._compile (internal/modules/cjs/loader.js:936:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:947:10)
    at Module.load (internal/modules/cjs/loader.js:790:32)
    at Function.Module._load (internal/modules/cjs/loader.js:703:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:999:10)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1325:8)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 3000
}

To Reproduce
Perform a fresh CI build.

Expected behavior
I would expect smoke tests to not throw any exceptions and confirm Dredd usable.


Since this is happening for a while, I wonder if that's an expected behavior. I would appreciate @honzajavorek involvement in this discussion.

@honzajavorek
Copy link
Contributor

This is a known issue of an unknown origin. Documented in apiaryio/dredd-example#36 and kind of in #1229 as well.

@honzajavorek
Copy link
Contributor

I'll close this as duplicate, but it's definitely a valid bug report.

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