Repository navigation
Retry to install proxies during already up-to-date self update - #1310
Conversation
|
I expected this to fail before this PR, but it already passes. So I don’t know if this PR actually fixes the problem. diff --git a/tests/cli-self-upd.rs b/tests/cli-self-upd.rs
index c8bc9c4b..3a24f93a 100644
--- a/tests/cli-self-upd.rs
+++ b/tests/cli-self-upd.rs
@@ -1273,5 +1273,12 @@ fn update_does_not_overwrite_rustfmt() {
"`rustfmt` is already installed");
assert!(rustfmt_path.exists());
assert_eq!(utils::file_size(rustfmt_path).unwrap(), 0);
+
+ // Remove the file as suggested by the error "already installed" error message.
+ utils::remove_file("rustfmt", rustfmt_path).unwrap();
+ assert!(!rustfmt_path.exists());
+
+ expect_ok(config, &["rustup", "self", "update"]);
+ assert!(rustfmt_path.exists());
});
} |
|
@SimonSapin it looks like the failures on CI may be related? |
837ecab to
ae57f64
Compare
CC rust-lang#1305 which this hopefully fixes.
ae57f64 to
a914469
Compare
|
Fixed. |
|
@SimonSapin it looks like unfortunately this causes what I think is perhaps more buggy behavior? Now every time I type |
|
Could you say more, maybe copy/paste the output? This PR hasn’t changed the code in |
|
Every self update looks like and every update looks like: where strace confirms the latter is indeed downloading/relinking rustup. |
|
https://static.rust-lang.org/rustup/release-stable.toml contains |
|
Urgh well that's a bummer :( Thanks for taking a look! |
|
Hm that doesn't seem to have fixed the issue though? |
|
Hm no wait hang on, that may be a cloudfront caching issue |
|
Deployed! |
|
I'm having this issue as well. At the last Executing Launching $ rustfmt
error: toolchain 'stable-x86_64-unknown-linux-gnu' does not have the binary `rustfmt`I get the same error for nightly |
|
@cbcoutinho that's actually expected (albeit not a great error message) You'll need to add the rustup component like so: and then you can execute it via |
|
Hmm, I tried this on macOS, but no luck: |
|
Oh, I'm guessing this might be because of a build failure? I seem to be missing rls as well since I ran |
|
|
|
Note that this PR is alleged to have caused #1316 |
Rel rust-lang/rustup#1316, testing fix from rust-lang/rustup#1310
CC #1305, which this hopefully fixes.