Repository navigation
Use a port picker to prevent port reuse #49
Description
Activity
What platform are you running the tests on? Also, how fast of a machine? I wonder if it isn't a race condition.
So I figured it out (and this is why I need to add instructions), but one of the tests attempts to connect to Redis, and another attempts to connect to memcached. Without both of those running, you'll get the
Error: bind EADDRINUSE null:8080error.- added a commit that references this issue
on Dec 14, 2015 - added a commit that references this issue
on Dec 14, 2015 - added a commit that references this issue
on Nov 9, 2022 - added a commit that references this issue
on Nov 9, 2022 - added 2 commits that reference this issue
on Nov 10, 2022 6 remaining items
- added a commit that references this issue
on Nov 17, 2022 - added 2 commits that reference this issue
on Nov 17, 2022 - added 2 commits that reference this issue
on Nov 17, 2022 - added 2 commits that reference this issue
on Nov 18, 2022 - added a commit that references this issue
on Nov 21, 2022
When running
npm test, at least one test appears to hold on to port 8080 causing later tests to fail.Rather than using port 8080 for all tests a port picker should be used for each test so that they don't interfere with each other.