-
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
[0.17.0] Error chmod-ing .bin files on 'yarn install' #1823
Comments
seeing the same issue on v0.17, was previously working on v0.16.1. Can post my error log if it helps. thanks! |
Same issue in Windows 10 using bash console. Also working ok in v0.16.1. |
same issue |
Same Issue working fine with 0.16.1 |
Same Issue |
Same Issue |
Same errore here: node: 6.7.0 |
We have |
We have also noticed the same issue with |
I can't reproduce this. |
Hi @bestander , You can use this steps to reproduce the bug: npm install -g [email protected]
git clone https://github.com/yarnpkg/yarn.git yarn-test
cd yarn-test
yarn install
node: v6.9.1 |
Could be related to #1863? |
@dbashford yeah, that could |
@pmoleri, I am on Mac and don't get an error like you but I get an unfinished install with a quick flash of error:
I am going to revert the change in #1210. |
It works. I tried this:
|
Ok, I'll merge it and make a 0.17.1 in a couple of hours On Tue, 15 Nov 2016 at 20:07, pmoleri [email protected] wrote:
|
Verified, working fine in v0.17.2 |
today same error with: Yarn version: Node version: Platform: |
Same error with:
I uploaded yarn-error-1823.log in a gist so you can get full log/package.json content... Running it again, it pass... |
Having the same problem with @francisoud and have tried both 0.22.0 and 0.26.1
Some builds pass while most fail. |
Same here after I ran
|
Do you want to request a feature or report a bug?
bug
What is the current behavior?
Running large install after updating to
0.17.0
, yarn erroring out at random times in the build runningchmod
on.bin
files. This works on0.16.1
1st run
2nd run
3rd run
If the current behavior is a bug, please provide the steps to reproduce.
Just running yarn on large project after cleaning out all the
node_modules
.What is the expected behavior?
Not erroring out
Please mention your node.js, yarn and operating system version.
v6.3.1
0.17.0
El Capitan
The text was updated successfully, but these errors were encountered: