Repository navigation
Conversation
|
I had a look at the output of Travis for some other PR and indeed it looks like issue #861 is fixed. |
|
It looks like curl is not installed on the Jenkins machine: |
|
The Travis builds failed with: |
|
that last travis failure is fixed by #1276 |
|
rebased on #1276 -- let's see what happens |
|
i think this is unrelated, but @chriscool thoughts on this failure? https://travis-ci.org/ipfs/go-ipfs/jobs/63627076#L2979 |
|
Odd, @travisperson take a look at: https://travis-ci.org/ipfs/go-ipfs/jobs/63627091 looks like your test fails? |
|
Here are the Travis errors now: |
|
@jbenet by the way above you ask me about https://travis-ci.org/ipfs/go-ipfs/jobs/63627091 which contains: but this is not the first error in the tests. There is one "not ok 22 - 'ipfs daemon' is ready" failure before. |
|
In fact both "not ok 22" errors contain the following line: so it looks like we have to randomize ports more or something like that. |
|
whats the status here? is this RFM? |
|
@whyrusleeping yeah, it would be nice if you could merge it as the Travis errors are not related. |
|
I get: locally in OSX. |
|
@jbenet maybe but the change made by this PR is at the bottom of t0060 (test number 13) while the "ipfs peer id looks good" is test number 4 in t0060, so it is not related to this PR. |
|
@jbenet by the way I tried to reproduce the "Error: no ipfs repo found in ..." on my Linux machine, by running |
|
Fixed by #1297 |
|
@chriscool if #1297 did not fix pls reopen. sorry for the delay |
This issue has been fixed by merging PR #1263 or PR #1238.
This fixes issue #861 (Strange error trying to run the daemon through supervisord).
License: MIT
Signed-off-by: Christian Couder chriscool@tuxfamily.org