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

Error when building in parallel: sh: 1: cargo: not found #496

Closed
probablykasper opened this issue Dec 8, 2020 · 5 comments
Closed

Error when building in parallel: sh: 1: cargo: not found #496

probablykasper opened this issue Dec 8, 2020 · 5 comments
Labels

Comments

@probablykasper
Copy link

When running cross in multiple instances at once, the following error shows up:

sh: 1: cargo: not found

If this is too difficult to fix, there could be an improved error, or a warning.

@probablykasper probablykasper changed the title Error when running cross in parallel: sh: 1: cargo: not found Error when building in parallel: sh: 1: cargo: not found Dec 8, 2020
@TarekkMA
Copy link
Contributor

I'm getting this error on GitHub action, I didn't run it in parallel

@cessen
Copy link

cessen commented Oct 2, 2021

I'm getting this error just with a plain cross build as well. Running NixOS. Seemingly can't use cross because of this error.

@cessen
Copy link

cessen commented Oct 2, 2021

It looks like this might be related to (or the same as) #260

@Alexhuszagh
Copy link
Contributor

If you're running NixOS, then yes it should be a duplicate of #260, but I don't believe the original error is. I'll see if I can replicate this in parallel.

@Alexhuszagh
Copy link
Contributor

I can't replicate this anymore, and cross doesn't use global state and only calls cargo and docker which have good consistency mechanisms.

@Alexhuszagh Alexhuszagh removed upstream A-container-engine Area: container engines labels Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants