chore: reduce concurrency to avoid bootstrap issues due to npm locks #3900
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It happens very frequently for me with `npm run update-packages`, which is also part of our release process. Sample error: lerna ERR! npm install exited 254 in '@loopback/service-proxy' lerna ERR! npm install stderr: npm ERR! code ENOENT npm ERR! syscall lchown npm ERR! path /Users/rfeng/.npm/_locks/staging-1f9c9b6dc2a3f888.lock npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, lchown '/Users/rfeng/.npm/_locks/staging-1f9c9b6dc2a3f888.lock' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
emonddr
approved these changes
Oct 9, 2019
|
Some folks, 2 years ago, would set concurrency to 1 : lerna/lerna#789 . |
|
|
|
Close it as |
|
Hmm, the problem comes back again. |
|
@raymondfeng . See my comment above. Perhaps try concurrency set to 1. Just as a test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It happens very frequently for me with
npm run update-packages, which is also part of our release process.Sample error:
Checklist
馃憠 Read and sign the CLA (Contributor License Agreement) 馃憟
npm testpasses on your machinepackages/cliwere updatedexamples/*were updated馃憠 Check out how to submit a PR 馃憟