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

Prevent rustup update to a toolchain without rustc or cargo. #1298

Merged
merged 2 commits into from
Dec 1, 2017
Merged

Prevent rustup update to a toolchain without rustc or cargo. #1298

merged 2 commits into from
Dec 1, 2017

Conversation

kennytm
Copy link
Member

@kennytm kennytm commented Nov 30, 2017

When the Rust CI is misconfigured, it is possible to produce a nightly where rustc or cargo is not available. This makes the entire toolchain unusable (for one day at least).

This PR tries to prevent the update operation from starting at all if these essential components are missing, so the user would still have a working though outdated toolchain.

Resolves #1297.

When the Rust CI is misconfigured, it is possible to produce a nightly
where `rustc` or `cargo` is not available. This makes the entire toolchain
unusable (for one day at least).

This PR tries to prevent the update operation from starting at all if
these essential components are missing, so the user would still have a
working though outdated toolchain.

Resolves #1297.
@alexcrichton
Copy link
Member

Awesome, thanks! It looks like though that maybe one test is failing on Linux? (although it could be spurious, I haven't checked the tests here in awhile)

@kennytm
Copy link
Member Author

kennytm commented Dec 1, 2017

+ cargo test --release -p download --target x86_64-unknown-linux-gnu
error: failed to write /src/Cargo.lock
Caused by:
  failed to open: /src/Cargo.lock
Caused by:
  Read-only file system (os error 30)

Doesn't seem like caused by me... The latest build in master is failing with the same error also.

@alexcrichton alexcrichton merged commit 1a2dd23 into rust-lang:master Dec 1, 2017
@alexcrichton
Copy link
Member

Ok, I think I know what's going on

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

Successfully merging this pull request may close these issues.

2 participants