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

Tests fail if a go-ipfs daemon is already running #3457

Closed
mib-kd743naq opened this issue Dec 2, 2016 · 3 comments
Closed

Tests fail if a go-ipfs daemon is already running #3457

mib-kd743naq opened this issue Dec 2, 2016 · 3 comments
Labels
topic/test failure Topic test failure

Comments

@mib-kd743naq
Copy link
Contributor

Version information:

Current master: a542dea5d

Type:

Bug

Priority:

P1

Description:

If an ipfs daemon is active TEST_NO_FUSE=1 make test fails like this
( tested only under the same user account, not sure what happens if the daemon runs under a dedicated/separate user but still occupies the usual ports )

@whyrusleeping whyrusleeping added the status/deferred Conscious decision to pause or backlog label Dec 12, 2016
@whyrusleeping
Copy link
Member

Thanks for reporting, This may have been fixed. Needs to be verified

@whyrusleeping whyrusleeping added need/verification This issue needs verification and removed status/deferred Conscious decision to pause or backlog labels Mar 6, 2017
@whyrusleeping whyrusleeping modified the milestones: Ipfs 0.4.7, Ipfs 0.4.8 Mar 6, 2017
@whyrusleeping whyrusleeping modified the milestones: Ipfs 0.4.9, Ipfs 0.4.8 Mar 24, 2017
@whyrusleeping whyrusleeping modified the milestones: Ipfs 0.4.10, Ipfs 0.4.9 May 8, 2017
@magik6k magik6k modified the milestones: Ipfs 0.4.10, Ipfs 0.4.11 Jul 28, 2017
@whyrusleeping
Copy link
Member

It appears that t0063 still fails if you have a daemon running locally while running the tests

@whyrusleeping whyrusleeping added topic/test failure Topic test failure and removed need/verification This issue needs verification labels Aug 28, 2017
@Kubuxu
Copy link
Member

Kubuxu commented Nov 6, 2017

I think it was resolved, I will try to check it once I am home.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic/test failure Topic test failure
Projects
None yet
Development

No branches or pull requests

5 participants
@whyrusleeping @Kubuxu @magik6k @mib-kd743naq and others