-
Notifications
You must be signed in to change notification settings - Fork 349
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
cargo miri setup fails with space in username #2417
Comments
This looks like #705. That has hopefully been fixed fairly recently. Your nightly is from before the fix landed. However I was never able to test the fix since I don't have a Windows machine, so if you could upgrade to a more recent nightly (anything from July should do it, 2022-07-19 is the most recent one you can use) and test if that helps, that would be great. :) |
rustc
Tried to reproduce but failed with another error: output
|
Hm, that looks like it got a lot further than before though, so that's good. I don't know what is then going wrong though, or whether it is related to the spaces. Can you do |
|
Hm, I still don't understand this error:
What does "never executed" mean? Is that a windows thing? Looks like the error is coming from cargo when it tries to invoke us as TARGET_RUNNER. Somehow that fails. |
Oh... looks like cargo does word-splitting on these TARGET_*_RUNNER variables. :( Unfortunately that is not something we can fix in Miri. I reported this as a bug against cargo: rust-lang/cargo#10892. Until that is fixed, Miri will not work on Windows if the path where rustup installed Rust contains a whitespace. |
@leontoeides @AngelicosPhosphoros the latest nightly should have a fix for this. Could you try this again? |
Excellent work! I am able to get further along now. This issue is closed for me |
New install of miri. Compiling under Windows 10 with
nightly-2022-03-10-x86_64-pc-windows-msvc
toolchain.When I run
cargo miri test
I get the following.It looks like the space in the folder name "C:\Users\My Name\.rustup" is causing problems.
The text was updated successfully, but these errors were encountered: