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

Browser tests failing on MacOS #206

Closed
richardschneider opened this issue Feb 17, 2018 · 9 comments
Closed

Browser tests failing on MacOS #206

richardschneider opened this issue Feb 17, 2018 · 9 comments
Assignees
Labels
exp/expert Having worked on the specific codebase is important kind/bug A bug in existing code (including security flaws) P2 Medium: Good to have, but can wait until someone steps up

Comments

@richardschneider
Copy link
Contributor

What is port 9999?

See build https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfsd-ctl/detail/graceful-stop/1/pipeline/14

Test Browser
listen EADDRINUSE 127.0.0.1:9999
Error: listen EADDRINUSE 127.0.0.1:9999
    at Object._errnoException (util.js:1031:13)
    at _exceptionWithHostPort (util.js:1052:20)
    at Server.setupListenHandle [as _listen2] (net.js:1367:14)
    at listenInCluster (net.js:1408:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1523:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:102:10)
error Command failed with exit code 1.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@richardschneider
Copy link
Contributor Author

@dryajov Any ideas? Haven't we seen this before?

@daviddias daviddias added kind/bug A bug in existing code (including security flaws) exp/expert Having worked on the specific codebase is important P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked labels Feb 19, 2018
@dryajov
Copy link
Member

dryajov commented Feb 19, 2018

I've pinged @victorbjelkholm about it on IRC - I believe he was to look into it. We can also change the default port for the http server to something more random, but I believe this indicates an issue somewhere else as well - ipfs/js-ipfs#1103 (comment)

@daviddias
Copy link
Member

image

@dryajov this is a ipfsd-ctl issue, also happening on Jenkins here - https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfsd-ctl/detail/PR-203/19/

Making it be a port random would only hide the issue, the real problem is that the http server is not closed properly.

@victorb
Copy link
Member

victorb commented Feb 22, 2018

@diasdavid I'm working on this right now.

Are you sure about the real problem? I'll make sure it's closed then, but it could also be that the port is used on macOS for other purposes. Real fix would be to make sure port is ephemeral + making sure server is closed IMHO.

@daviddias
Copy link
Member

but it could also be that the port is used on macOS for other purposes.

You can test this easily by changing the port number. If it works, then it closes it properly :)

@daviddias
Copy link
Member

Update: Let's see #209 :)

@victorb
Copy link
Member

victorb commented Feb 22, 2018

Fair enough. My theory is that tests were killed in a stage where the http-server was not properly killed, but this doesn't happen always, just sometimes (cancelled builds?).

@daviddias
Copy link
Member

Verdict: #209 (comment)

@daviddias
Copy link
Member

This was fixed.

@ghost ghost removed the status/ready Ready to be worked label Mar 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/expert Having worked on the specific codebase is important kind/bug A bug in existing code (including security flaws) P2 Medium: Good to have, but can wait until someone steps up
Projects
None yet
Development

No branches or pull requests

4 participants