Getting CI green

[vmx]

This is a meta issue to collect all the PRs to get the CI Green

• Use a different remote server for test #711
• fix: don't error to specific interface-js-ipfs-core#235
• fix: fix broken stats test interface-js-ipfs-core#236
• Fix of complete files.stat with the 'with-local' option interface-js-ipfs-core#227 (comment)
• npm missing on macos worker jenkins#95
• Fix of DHT provide test is broken #715
• tests: Increase .dht .query timeout interface-js-ipfs-core#238
• test: increase Karma timeout #716
• Harden DHT tests interface-js-ipfs-core#239

[daviddias]

@vmx double check, but I think you also need #695

[vmx]

@diasdavid So far it doesn't seem that I need #695, except if it fixes ipfs-inactive/interface-js-ipfs-core#227 (i haven't tried yet)

[vmx]

With the outstanding PRs merged and these three reverted:

• a10e3d5
• b08f21a
• ipfs-inactive/interface-js-ipfs-core@de72184

CI is quite often green. It's still not reliable, but as different tests are failing I'd consider them environment issues.

[vmx]

@diasdavid Everything from my side is merged now. The test runs are quite stable now. Now only the tests broken by the commits mentioned above need to be fixed. Who will fix those? The authors of those commits?

Edit: This is what it looks like without those commits reverted https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfs-api/detail/get-ci-green/70/tests

[daviddias]

@vmx would you have the chance to fix those too? thanks!

[vmx]

@diasdavid Not sure when, but I can have a look if it isn't fixed in the meantime.

[daviddias]

@vmx I went through it. the files.stat was failing because it was expecting features that haven't been released on go-ipfs. ALl good now :)