Skip to content
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

more Extracting tar content of undefined failed woes in yarn 1.17.3 #7544

Open
dagda1 opened this issue Sep 12, 2019 · 8 comments
Open

more Extracting tar content of undefined failed woes in yarn 1.17.3 #7544

dagda1 opened this issue Sep 12, 2019 · 8 comments

Comments

@dagda1
Copy link

dagda1 commented Sep 12, 2019

I am using yarn 1.17.3

Do you want to request a feature or report a bug?
bug

What is the current behavior?

An example of what is happening is here:

Intermittent Extracting tar content of undefined failed, the file appears to be corrupt: "EEXIST: file already exists, mkdir '/home/jenkins-slave/.cache/yarn/v4/npm-body-parser-1.18.3-5b292198ffdd553b3a0f20ded0592b956955c8b4/node_modules/body-parser'"

Happens occasionally and can be any dependency.

There are many, many, many similar issues on the issue tracker including #7087, #6755, #6312

Most say it is a git URL in the package.json or lock file but I don't have any of those.

Other solutions say to use yarn install --network-concurrency 1

But this is a poor solution in a CI pipeline with lots of builds at any time.

If the current behavior is a bug, please provide the steps to reproduce.

I cannot reproduce it consistently, seems to happen when the CI server isunder load.

What is the expected behavior?

No cache problems

Please mention your node.js, yarn and operating system version.

node 8.11.3

@iamdanie
Copy link

iamdanie commented Dec 4, 2019

+1 . Happening with Bitrise CI

@dannycoulombe
Copy link

Same happening here..

@arikanmstf-tw
Copy link

having the same issue with yarn 1.22.4

@alecgerona
Copy link

Happening with yarn 1.22.4. Gitlab CI. Not reproducible on local machine however.

@ohana54
Copy link

ohana54 commented Jun 26, 2020

FYI, I attempted to solve one of the root causes for this issue in #8182, still waiting for someone to review it.

@alecgerona
Copy link

For anyone still needing a solution, I've changed our git repo dependency to remove its prepare/postinstall scripts and just commit the dist folder for them.

@curiousercreative
Copy link

Also experiencing on 1.22.4 and like @alecgerona it seems to coincide with a package that has a prepare script. Running yarn install enough times and one install succeeded :(

@nathanKramer
Copy link

I've been having this issue and fixed it by moving from a parallel install of dependencies to synchronous (two different yarn install commands for a server/client in a mono-repo).

Not sure if that will be helpful to anyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants