-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
074b166
to
394200a
Compare
rebased master onto this branch so that CI is happy |
circle.yml
Outdated
- sudo apt-get update | ||
- sudo apt-get install -f || true | ||
- sudo dpkg -i libnss3*.deb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@victorbjelkholm this is breaking chrome on CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@diasdavid yeah, because js-ipfs is still using old Ubuntu version (on CircleCI). Once this PR is ready to be merged (all CIs except CircleCI passing), we'll upgrade the version and confirm all CIs again and then merge this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if you need me to do something or if it is all part of your plan. Let me know if you need my help :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@victorbjelkholm shall I go ahead and merge this PR?
394200a
to
17f4d1d
Compare
Codecov Report
@@ Coverage Diff @@
## master #1103 +/- ##
=========================================
Coverage ? 83.68%
=========================================
Files ? 122
Lines ? 2752
Branches ? 0
=========================================
Hits ? 2303
Misses ? 449
Partials ? 0 Continue to review full report at Codecov.
|
@victorbjelkholm any update here? |
17f4d1d
to
e21c8f1
Compare
@victorbjelkholm you will have to rebase master onto this branch. |
e21c8f1
to
d6d1e4e
Compare
Just rebaed it for you :) |
9aec32d
to
a7de496
Compare
Just missing one test case on windows to be ready to merge. Failing case:
|
Hm, seems I got confused by the large stacktrace in the test output, and there is lots more of windows tests failing. Could we get some help from @richardschneider or @hacdias maybe? |
@victorbjelkholm Starting to look at the issues! |
a7de496
to
e30a2c9
Compare
@richardschneider did you had time to check this? |
@diasdavid I think #1159 resolved the issues. Please tell me if any more issues exist. |
e30a2c9
to
069c2e4
Compare
All right, just rebased master onto this one. Let's see :) |
Weird, Jenkins disappeared from the list (the one not showing is just Node Security) |
069c2e4
to
5d56dfc
Compare
@victorbjelkholm what's up with Jenkins? |
@diasdavid from the last rows in the output, it's a merge conflict. Github also confirms this is a merge conflict. I'll figure out the resolution of this today. |
@victorbjelkholm Jenkins is showing some new failtures after the .gitignore but that are unrelated. Have you seen these? |
16e393d
to
d16727d
Compare
Ah, I think the real problem from here -- #1103 (comment) -- is that now the tests are running over the repo that should be just used to be c&p to a tmp folder but that with #1234 it stopped being, since the ncp + rimraf was removed. @dryajov wanna fix that? |
Just Windows issues left -- https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfs/detail/PR-1103/73/tests -- and timeouts on Travis -- https://travis-ci.org/ipfs/js-ipfs/builds/346889245#L6612-L6626. |
@victorbjelkholm I think they are mostly related to gratious shutdown. |
@dryajov didn't everyone agree that any ipfs shutdown related issue (which will be fixed post release) should be/is skipped? |
@diasdavid it makes total sense, but I didn't hear we were actually doing |
BTW, I think we should just merge as we know what the issues are and are already handling them elsewhere. Here is my 👍 |
Ah, #1103 (comment), I wasn't in that standup. Gonna skip them. |
@dryajov we are not doing a release with red CI (except for Appveyor, thanks go-ipfs 0.4.13..). Travis is failing one of the highlights of this release is faster CI through Jenkins. |
@diasdavid I traced it back to the relevant convo - #1103 (comment). I'm skipping those tests that will fail due to lack of gracious stop. |
All is green. |
Seems that it is passing again :) might have been a hiccup. |
Flaky tests be flaky! But yay, Jenkins 🎉 |
This is a round up of the remaining async/await PRs along with some cleanup and docs fixes. resolves ipfs#1103 resolves ipfs-inactive/js-ipfs-http-client#1122 resolves ipfs-inactive/js-ipfs-http-client#1158 (hopefully!) closes ipfs-inactive/js-ipfs-http-client#1164 closes ipfs-inactive/js-ipfs-http-client#1165 closes ipfs-inactive/js-ipfs-http-client#1166 closes ipfs-inactive/js-ipfs-http-client#1169 closes ipfs-inactive/js-ipfs-http-client#1170 closes ipfs-inactive/js-ipfs-http-client#1172 BREAKING CHANGE: The `log.tail` method now returns an async iterator that yields log messages. Use it like: ```js for await (const message of ipfs.log.tail()) { console.log(message) } ``` BREAKING CHANGE: The response to a call to `log.level` now returns an object that has camel cased keys. i.e. `Message` and `Error` properties have changed to `message` and `error`. BREAKING CHANGE: Dropped support for go-ipfs <= 0.4.4 in `swarm.peers` response. BREAKING CHANGE: The signature for `ipfs.mount` has changed from `ipfs.mount([ipfsPath], [ipnsPath])` to `ipfs.mount([options])`. Where `options` is an optional object that may contain two boolean properties `ipfsPath` and `ipnsPath`. The response object has also changed to be camel case. See https://docs.ipfs.io/reference/api/http/#api-v0-mount. BREAKING CHANGE: Default ping `count` of 1 in client has been removed. The default ping count is now whatever the IPFS node defaults it to (currently 10). If you specifically need 1 ping message then please pass `count: 1` in options for `ipfs.ping()`. BREAKING CHANGE: Multi parameter constructor options are no longer supported. To create a new IPFS HTTP client, pass a single parameter to the constructor. The parameter can be one of: * String, formatted as one of: * Multiaddr e.g. /ip4/127.0.0.1/tcp/5001 * URL e.g. http://127.0.0.1:5001 * [Multiaddr](https://www.npmjs.com/package/multiaddr) instance * Object, in format of either: * Address and path e.g. `{ apiAddr: '/ip4/127.0.0.1/tcp/5001': apiPath: '/api/v0' }` (Note: `apiAddr` can also be a string in URL form or a Multiaddr instance) * Node.js style address e.g. `{ host: '127.0.0.1', port: 5001, protocol: 'http' }`
This commit updates all CI scripts to the latest version