-
Notifications
You must be signed in to change notification settings - Fork 62
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
Comments
@dryajov Any ideas? Haven't we seen this before? |
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) |
@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. |
@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. |
You can test this easily by changing the port number. If it works, then it closes it properly :) |
Update: Let's see #209 :) |
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?). |
Verdict: #209 (comment) |
This was fixed. |
What is port 9999?
See build https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfsd-ctl/detail/graceful-stop/1/pipeline/14
The text was updated successfully, but these errors were encountered: