-
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
[BUG] yarn runs node-gyp operations in parallel which can cause file lock error on ~/.node-gyp resources and fail #2429
Comments
@kittens @bestander this issue is blocking on using yarn in our project. Can you please help with this issue? Is there a way to run node-gyp on packages sequentially to avoid this issue temporarily? |
Now that we have a workaround with CHILD_CONCURRENCY. |
Is there a node-gyp issue for this? |
Here #1874 and here nodejs/node-gyp#1054 |
Ah, so no consensus as to where this should be fixed? |
Help from the community is needed. |
How about disabling parallel builds on Windows until we have an option. I'm sure most would prefer slightly slower installs over intermittent install failures without using an environment variable! |
This is configured via |
untested workaround for yarnpkg/yarn#2429 , aka our bcrypt/node-gyp issue pro: no more node-gyp failures con: native modules are compiled serially, so that step will take longer
Closing as a duplicate of #1874. |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
yarn installation with certain packages causes EBUSY error in node-gyp step. Perhaps due to Yarn trying to install all native modules simultaneously while
npm i
installs them synchronously.If the current behavior is a bug, please provide the steps to reproduce.
run
yarn
in a directory with the following package.json:What is the expected behavior?
yarn installation of native packages is not impacted by how many/which other native packages are compiling at the same time.
Please mention your node.js, yarn and operating system version.
node: 6.2.2
OS: Windows x64 10.0.14393
Yarn: 0.18.1 (installed via
npm i -g yarn
)detailed output
output from
yarn
:note that
npm i
in the same directory seems to run without error:The text was updated successfully, but these errors were encountered: