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.

Sign up for GitHub

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

Jump to bottom

Cross fails with error: "rustup" "target" "list" failed with exit code: Some(1) #634

Closed
asomers opened this issue Jun 28, 2017 · 2 comments
Closed

Cross fails with error: "rustup" "target" "list" failed with exit code: Some(1) #634

asomers opened this issue Jun 28, 2017 · 2 comments
Assignees
@asomers
Labels
A-testing

Comments

@asomers
Copy link
Member

asomers commented Jun 28, 2017

On about 25-June, all of our Travis builds started to fail with the error message:

error: "rustup" "target" "list" failed with exit code: Some(1)

I don't know why it started on 25-June. It's probably either a change to Travis (they updated their builders, but they claim it was done by 21-June), or Rustup, or Cross. We should also report this bug upstream to japaric/cross
https://travis-ci.org/nix-rust/nix/builds/246718360
@asomers asomers self-assigned this Jun 28, 2017
asomers added a commit to asomers/nix that referenced this issue Jun 28, 2017
@asomers
Install a default rust toolchain before testing in Travis
dec97b5 
Cross crashes if there isn't a default toolchain installed, even if it's
not the toolchain we intend to use.

Fixes nix-rust#634
This was referenced Jun 28, 2017
Closed
Closed
@Susurrus Susurrus mentioned this issue Jun 30, 2017
Merged
@asomers
Copy link
Member Author

asomers commented Jul 1, 2017

Turns out that Travis was cacheing our .cargo and target directories (because we told it to). When rustup 1.5.0 came out on 24-June, that broke the build. Something in our .cargo didn't like it, I guess. Through the Travis control panel, I cleared our caches, and the problem is resolved.

@asomers asomers closed this as completed Jul 1, 2017
@asomers asomers mentioned this issue Jul 1, 2017
Merged
@casey
Copy link

casey commented Sep 8, 2017

My nightly builds started failing, and clearing the cache was the solution.

Thanks for posting this issue, along with how to fix it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@asomers asomers

Labels
A-testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@casey @asomers