-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression between 0.16.1 and 0.17.0 when building package using node-gyp? #1838
Comments
Until this is fixed, you can temporarily roll back by doing this instead of
I'll work on keeping multiple versions of Yarn in the Debian repo to make it easier in the future. |
Sure that's what I am doing. Thanks! |
0.17.3 should fix it, can you please confirm? |
@bestander worked for me, but I had to |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Cannot run
yarn
on Travis-CI with 0.17.0If the current behavior is a bug, please provide the steps to reproduce.
Install yarn with the recommended method
https://github.com/MoOx/phenomic/blob/9c63590fad541ff7be9af237954704fe4df88815/.travis.yml#L13-L20
(get 0.17.0)
https://travis-ci.org/MoOx/phenomic/jobs/175953792#L668
Run
yarn
and wait for failure because of leveldownhttps://travis-ci.org/MoOx/phenomic/jobs/175953792#L681
What is the expected behavior?
Not fatal error, this was totally ok with 0.16.1 a day before
https://travis-ci.org/MoOx/phenomic/jobs/175489470#L805
(not that if you check my build history, you will find some yarn install passing using 0.17.0 but this was due to travis cache I setup for node_modules. Since I cleaned the cache (for another failure I was suspecting), I cannot make
yarn
work.Please mention your node.js, yarn and operating system version.
$ node --version
v6.9.1
$ npm --version
3.10.8
$ nvm --version
0.32.0
yarn 0.17.0
The text was updated successfully, but these errors were encountered: