-
Notifications
You must be signed in to change notification settings - Fork 892
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
rustup update error #1316
Comments
I'm getting the same thing. Win 10, 64 bit. |
Seeing this on Windows 7 x64 for cargo, cargo-fmt, rls, rustc, rustdoc, rustfmt, rust-gdb, and rust-lldb |
I don't know if it is relevant but cargo is not finding |
Getting the same error:
|
I ran into the same problem. In "raw.rs" the function hardlink tries to unlink the destinaton file but does not care about the io::Result. This call fails on my system. Any attempt to link the file fails due to an already existing file. As far as I understand informations from MSDN right now hardlinks are not removeable when the the file is locked. It seems to be locked due to running rustup.exe.
|
Possibly related. Running
Downloading
Running
|
Yeah, I can confirm that |
Me too (also win 10 x64) |
We're seeing the same failure across many AppVeyor builds, eg.
Any solves or workarounds would be very welcome -- this is a blocking issue for many of our projects. |
Confirm. |
Confirm, |
I do have the same issue too. |
Same issue |
Same here Win10 x64 (17063):
Removed 'rustfmt' and 'cargo-fmt' as indicated, then:
|
Rel rust-lang/rustup#1316, testing fix from rust-lang/rustup#1310
Confirm, Windows 10 x64, and given the stack trace
|
To downgrade appveyor to older version, use
|
I think there are some changes about how Windows handle the path and link, you may reference URLs below: [Stable] ICE on Windows 7 when compiling dependencies · Issue #45067 Naming Files, Paths, and Namespaces (Windows) How to Make Windows 10 Accept File Paths Over 260 Characters CreateHardLink function (Windows) Workaround for >1023 hard links on Windows platforms |
I am also getting this. Windows 10, 64 bit.
|
I began receiving this error after adding the rls-preview component. Not sure if that is related however. nightly-x86_64-pc-windows-msvc unchanged - rustc 1.24.0-nightly (2dad872a2 2017-12-29) |
I'm getting a similar error:
I noticed that the last error messages appear after a new prompt, after rustup.exe has exited. This seems to indicate that the failing operation is done in a subprocess. Looking at Procmon output this is indeed the case:
That last last command is done after "rustup.exe" exits in self_update.rs: #[cfg(windows)]
pub fn self_replace() -> Result<()> {
try!(wait_for_parent());
try!(install_bins());
Ok(())
} This code hasn't been changed for a long time, so I don't know why it started failing now for me, but I think there is a race condition: The executable file is not immediately accessible after the process has exited. (This presentation and the similarly named Youtube video give interesting facts about e.g. the asynchronous nature of file deletion in Windows: Racing the Filesystem by Niall Douglas.) I would try to have a sleep/retry loop around |
Fresh install WIN10 Enterprise λ rustup -v update stable-x86_64-pc-windows-msvc unchanged - rustc 1.22.1 (05e2e1c41 2017-11-22) error: could not create link from 'C:\Users\user.cargo\bin\rustup.exe' to 'C:\Users\user.cargo\bin\rustc.exe' |
Same^^^ |
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
Fix self update errors filling in missing proxies The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes #1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
Fix self update errors filling in missing proxies The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes #1316
I still get |
@Yanpas an updated version of rustup had not been released, it shoudl be fixed now. |
Having this issue. Was on a pretty old version of rustup and updated recently. GOt the warnings about rustfmt and cargo-fmt, complied, and suffered. The error:
Attempt to solve:
Version:
|
@hherman1 Perhaps you commented on the wrong issue. Anyway you're trying to add a component named |
The previous logic had some subtle bugs for a number of reasons, and hopefully this iteration irons them out. Closes rust-lang#1316
I just got the same error updating to 1.30.
Also after trying
Since the issue was closed about 1 year ago tell me if you prefer that I open a new one. |
I get this error today:
Don't know what it means just reporting.
Win 10, 64 bit.
The text was updated successfully, but these errors were encountered: