-
Notifications
You must be signed in to change notification settings - Fork 348
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
Miri tests on Windows require admin for symlinks #3587
Comments
I'll look into this later if there is a shim missing |
Does |
Yes, that is the first case. |
Tests also pass when cross-interpreting |
Ah, sorry, I read too quickly. Well that's something at least. :) So there's a problem creating symlinks. Wasn't there something where creating symlinks on Windows needs admin permissions or so? It works on CI though... We should definitely do a better job at saying what the error was, though...
The directory gets cleaned up when tests are done (even if they fail), so you wouldn't see any trace of that. If it gets to test_symlink it means these other tests already passed
So I think it's safe to say the directory exists and works as expected, just symlinks don't. |
TBH I have no idea how symlinks work on Windows. I've never used them. And since you mentioned it, I ran the tests under admin and they passed. So yeah, that seems to be correct. |
Okay, good to know that we figured out the cause of this. :) Not sure what the best way is to deal with this. We could ignore permission errors (if we can detect them, @ChrisDenton do you have any better ideas? |
You can enable "developer mode" in settings to allow unprivileged symlinks creation. So one option would just be to document this as a requirement. Otherwise maybe there could be a check to see if the host supports symlinks (e.g. by trying to create one)? |
io::Error handling: keep around the full io::Error for longer so we can give better errors This should help with the error message in #3587.
With #3589 it does make it clearer. At least it is an error code that google can tell me about.
|
Thanks for checking that!
|
do not run symlink tests on Windows hosts Fixes #3587
io::Error handling: keep around the full io::Error for longer so we can give better errors This should help with the error message in rust-lang/miri#3587.
do not run symlink tests on Windows hosts Fixes rust-lang/miri#3587
This is on Windows 10 on commit 28ab963. I can replicate the issue on both of my computers.
.\miri toolchain
.\miri test
Tests pass successfully
.\miri toolchain
$Env:MIRI_TEST_TARGET="x86_64-unknown-linux-gnu"
.\miri test
This seems to happen on *nix targets as it happens on
*-apple-darwin
as well.Based upon the instructions inside the test I looked for
miri_
files, but there were none in the tmp directory. Also setting TMPDIR or MIRI_TEMP to other paths had no affect.The text was updated successfully, but these errors were encountered: