-
Notifications
You must be signed in to change notification settings - Fork 300
Conversation
Something weird happened with #669 and code is missing causing these errors:
Could you check what's happening? Also @dryajov |
@diasdavid I believe I know what the issue with the PR is - we need to use the current
I'm making the change right now. |
the relevant line in the above comment is |
depends on ipfs-inactive/interface-js-ipfs-core#203 |
cb8257b
to
43f4891
Compare
released the fixed interface-ipfs-core and spinned up the CI here again. Waiting to get a confirmation. |
@diasdavid looking into ci issues |
@diasdavid @victorbjelkholm something is up with jenkins, the builds are not running. |
hmm, travis is giving a |
I'll profile the test run tomorrow see where things might be going wrong. |
btw, coverage is back to a reasonable level. |
requires - ipfs/js-ipfsd-ctl#184 |
What created the massive drop? |
released ipfs/js-ipfsd-ctl#184, spinning CI here again |
It was due to the fact that ipfs-api was not being consumed directly, but through ipfsd-ctl which was wrong in the context of ipfs-api testing. Ding IpfsApi(ipfsd-ctl.apiAddr) fixes that. |
Every CI is failing. Circle with:
Travis runs out of memory. I believe that it is trying to webpack stuff it doesn't need and crashes because of that. |
@diasdavid There seem to be two issues with the tests, at least in circleci - travis seems to be failing on a different error
I haven't been able to reproduce either of this failures locally, so it makes it a little harder to troubleshoot. I can run the builds with ssh enabled, which should allow me to trouble shoot it on circle directly. |
ok, increasing the |
Ok, only tests missing is the Windows PubSub failing tests. LGTM :) |
ref: #652