Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Updating CI files #1103

Merged
merged 12 commits into from
Feb 28, 2018
Merged

Updating CI files #1103

merged 12 commits into from
Feb 28, 2018

Conversation

victorb
Copy link
Member

@victorb victorb commented Nov 22, 2017

This commit updates all CI scripts to the latest version

@ghost ghost assigned victorb Nov 22, 2017
@ghost ghost added the status/in-progress In progress label Nov 22, 2017
@daviddias daviddias force-pushed the automatic-ci-script-update branch from 074b166 to 394200a Compare November 23, 2017 11:30
@daviddias
Copy link
Member

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
Copy link
Member

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

Copy link
Member Author

@victorb victorb Nov 23, 2017

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.

Copy link
Member

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 :)

Copy link
Member

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?

@victorb victorb force-pushed the automatic-ci-script-update branch from 394200a to 17f4d1d Compare November 23, 2017 15:32
@codecov
Copy link

codecov bot commented Nov 23, 2017

Codecov Report

❗ No coverage uploaded for pull request base (master@e7f0432). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e7f0432...2b3b21c. Read the comment docs.

@daviddias
Copy link
Member

@victorbjelkholm any update here?

@daviddias daviddias force-pushed the automatic-ci-script-update branch from 17f4d1d to e21c8f1 Compare December 2, 2017 15:21
@ghost ghost assigned daviddias Dec 2, 2017
@daviddias
Copy link
Member

@victorbjelkholm you will have to rebase master onto this branch.

@daviddias daviddias force-pushed the automatic-ci-script-update branch from e21c8f1 to d6d1e4e Compare December 10, 2017 09:32
@daviddias
Copy link
Member

Just rebaed it for you :)

@daviddias daviddias removed their assignment Dec 11, 2017
@victorb victorb force-pushed the automatic-ci-script-update branch 2 times, most recently from 9aec32d to a7de496 Compare December 18, 2017 09:04
@victorb
Copy link
Member Author

victorb commented Dec 18, 2017

Just missing one test case on windows to be ready to merge.

Failing case:

  15) cli
       init
         basic:

      AssertionError: expected '' to equal 'Hello and Welcome to IPFS!\n\n██╗██████╗ ███████╗███████╗\n██║██╔══██╗██╔════╝██╔════╝\n██║██████╔╝█████╗  ███████╗\n██║██╔═══╝ ██╔══╝  ╚════██║\n██║██║     ██║     ███████║\n╚═╝╚═╝     ╚═╝     ╚══════╝\n\nIf you\'re seeing this, you have successfully installed\nIPFS and are now interfacing with the ipfs merkledag!\n\n -------------------------------------------------------\n| Warning:                                              |\n|   This is alpha software. Use at your own discretion! |\n|   Much is missing or lacking polish. There are bugs.  |\n|   Not yet secure. Read the security notes for more.   |\n -------------------------------------------------------\n\nCheck out some of the other files in this directory:\n\n  ./about\n  ./help\n  ./quick-start     <-- usage examples\n  ./readme          <-- this file\n  ./security-notes\n'
      + expected - actual

      +Hello and Welcome to IPFS!
      +
      +██╗██████╗ ███████╗███████╗
      +██║██╔══██╗██╔════╝██╔════╝
      +██║██████╔╝█████╗  ███████╗
      +██║██╔═══╝ ██╔══╝  ╚════██║
      +██║██║     ██║     ███████║
      +╚═╝╚═╝     ╚═╝     ╚══════╝
      +
      +If you're seeing this, you have successfully installed
      +IPFS and are now interfacing with the ipfs merkledag!
      +
      + -------------------------------------------------------
      +| Warning:                                              |
      +|   This is alpha software. Use at your own discretion! |
      +|   Much is missing or lacking polish. There are bugs.  |
      +|   Not yet secure. Read the security notes for more.   |
      + -------------------------------------------------------
      +
      +Check out some of the other files in this directory:
      +
      +  ./about
      +  ./help
      +  ./quick-start     <-- usage examples
      +  ./readme          <-- this file
      +  ./security-notes
      
      at ipfs.then.then (test\cli\init.js:47:37)
      at <anonymous>
      at process._tickDomainCallback (internal/process/next_tick.js:228:7)

@victorb
Copy link
Member Author

victorb commented Dec 18, 2017

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?

@richardschneider
Copy link
Contributor

@victorbjelkholm Starting to look at the issues!

@victorb victorb force-pushed the automatic-ci-script-update branch from a7de496 to e30a2c9 Compare December 22, 2017 09:57
@daviddias
Copy link
Member

@richardschneider did you had time to check this?

@richardschneider
Copy link
Contributor

@diasdavid I think #1159 resolved the issues. Please tell me if any more issues exist.

@daviddias daviddias force-pushed the automatic-ci-script-update branch from e30a2c9 to 069c2e4 Compare December 28, 2017 08:45
@ghost ghost assigned daviddias Dec 28, 2017
@daviddias
Copy link
Member

All right, just rebased master onto this one. Let's see :)

@daviddias
Copy link
Member

daviddias commented Dec 28, 2017

Weird, Jenkins disappeared from the list (the one not showing is just Node Security)

image

@victorbjelkholm ?

@victorb victorb force-pushed the automatic-ci-script-update branch from 069c2e4 to 5d56dfc Compare December 28, 2017 11:31
@daviddias
Copy link
Member

@victorbjelkholm what's up with Jenkins?

image

@victorb
Copy link
Member Author

victorb commented Jan 23, 2018

@diasdavid from the last rows in the output, it's a merge conflict. Github also confirms this is a merge conflict.

image

I'll figure out the resolution of this today.

@daviddias
Copy link
Member

@victorbjelkholm Jenkins is showing some new failtures after the .gitignore but that are unrelated. Have you seen these?

@daviddias daviddias force-pushed the automatic-ci-script-update branch from 16e393d to d16727d Compare February 27, 2018 14:03
@daviddias
Copy link
Member

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?

@ghost ghost assigned dryajov Feb 27, 2018
@daviddias
Copy link
Member

daviddias commented Feb 27, 2018

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.

@dryajov
Copy link
Member

dryajov commented Feb 27, 2018

@victorbjelkholm I think they are mostly related to gratious shutdown.
screen shot 2018-02-27 at 12 29 01 pm

@daviddias
Copy link
Member

@dryajov didn't everyone agree that any ipfs shutdown related issue (which will be fixed post release) should be/is skipped?

@dryajov
Copy link
Member

dryajov commented Feb 27, 2018

@diasdavid it makes total sense, but I didn't hear we were actually doing this.skip() on them.

@dryajov
Copy link
Member

dryajov commented Feb 27, 2018

BTW, I think we should just merge as we know what the issues are and are already handling them elsewhere.

Here is my 👍

@dryajov
Copy link
Member

dryajov commented Feb 27, 2018

Ah, #1103 (comment), I wasn't in that standup. Gonna skip them.

@daviddias
Copy link
Member

@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.

@dryajov
Copy link
Member

dryajov commented Feb 27, 2018

@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.

@dryajov
Copy link
Member

dryajov commented Feb 27, 2018

Last run on jenkins was successful

screen shot 2018-02-27 at 5 17 32 pm

Also, we seem to have green CI all around (except for travis PR which is still going)

screen shot 2018-02-27 at 5 19 12 pm

@dryajov
Copy link
Member

dryajov commented Feb 27, 2018

All is green.

@daviddias
Copy link
Member

Rerun everything again, failed:
image

@daviddias
Copy link
Member

Seems that it is passing again :) might have been a hiccup.

@daviddias daviddias merged commit bc66e9f into master Feb 28, 2018
@ghost ghost removed the status/in-progress In progress label Feb 28, 2018
@daviddias daviddias deleted the automatic-ci-script-update branch February 28, 2018 01:33
@victorb
Copy link
Member Author

victorb commented Feb 28, 2018

Flaky tests be flaky! But yay, Jenkins 🎉

MicrowaveDev pushed a commit to galtproject/js-ipfs that referenced this pull request May 22, 2020
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' }`
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P0 Critical: Tackled by core team ASAP
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants