-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Try to improve the npm cache situation in CI #35081
Conversation
# A "full" install is executed, since `npm ci` does not always exit | ||
# with an error status code if the lock file is inaccurate. | ||
# | ||
# See: https://github.com/WordPress/gutenberg/issues/16157 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the time it passed since that issue was created, I'm assuming that the issue is fixed (we were still in travis) but we'll see.
d74bd60
to
aaaad43
Compare
Size Change: 0 B Total Size: 1.06 MB ℹ️ View Unchanged
|
a3e9b51
to
a125c6b
Compare
It looks like we still have the npm error 😕 |
Yeah, I tried several things and I can't explain why this fails :( |
385652e
to
b55eaee
Compare
b55eaee
to
967eb32
Compare
It seems the issue is specific to the git based dependencies, so closing in favor of #34886 |
closes #16157
npm install have been failing too much lately in CI and we don't really know the reasons yet, this PR is mostly "try and fail" work, I've did two things for now: