This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Pick random ports on tests #90
Labels
exp/expert
Having worked on the specific codebase is important
Comments
go-ipfs doesn't use port 0 for the Gateway, which is where that is failing.
It is strange however, because I changed the config to launch the http-api on port 9090 to avoid those kind of collisions, but it seems that you had something else running on port 9090? |
It does for tests (https://github.com/ipfs/go-ipfs/blob/master/test/sharness/lib/test-lib.sh#L149), and we should too. I run other software on 8080, so I run the gateway on 9090, as may many other users -- 8080 is pretty popular and 9090 is the next most "logical" choice. ;) |
daviddias
changed the title
Tests fail if there is already an ipfs daemon running on the system
Pick random ports on tests
Mar 21, 2016
Got it, could you submit a PR for that? |
daviddias
added
enhancement
exp/novice
Someone with a little familiarity can pick up
labels
Mar 21, 2016
hackergrrl
added
help wanted
exp/expert
Having worked on the specific codebase is important
and removed
exp/novice
Someone with a little familiarity can pick up
labels
Mar 21, 2016
This isn't on my short term list, so let's open it up as |
Took a shot at it, was actually playing with this last night. |
thank you :) |
This was referenced Nov 27, 2023
This was referenced Nov 28, 2023
This was referenced Feb 11, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We ought to gracefully use port zero (like go-ipfs).
The text was updated successfully, but these errors were encountered: