-
Notifications
You must be signed in to change notification settings - Fork 2
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
xfail symlink tests in hole2 #27
Comments
I am running with miniconda in windows terminal. The test failures are:
and
|
If we cannot create symlinks (under some conditions) on Windows then that would imply that the code |
I'll tag @lilyminium here - I can't remember the specifics but I thought Lily mentioned that the issue is something that's down to the install/environment not the code itself, maybe we should fail more graciously though. |
Ummm, it looks like the test already predicts the symlink permissions error. I think if you ran with admin permissions then you can symlink. https://www.scivision.dev/windows-symbolic-link-permission-enable/ also has something about running in "Developer mode", although that might (?) require 3.8+. It's hard to say without knowing more about Windows but IMO this should be treated as a bug, the file should be copied instead of symlinked, and just deleted after. Annoyingly, I think this function might have been required in the first place because Windows had a (weirdly short, too) max path length.
From the looks of the xfail I thought this was a problem only for win32 and also expected virtually no one to use win32. I don't think tests would be run with admin permissions either, but you probably don't want to run Python like that anyway.... |
Expected behavior
All tests should pass.
Actual behavior
On Windows it's quite common for folks to get permission errors on symlink creation leading to test failures.
Since it's a known failure, it would be good if we just xfailed the relevant tests.
Code to reproduce the behavior
run tests on win 10 or 11 (in my case using anaconda prompt, not sure about @jbarnoud)
Current version of MDAnalysis
python -V
)? 3.7-3.10The text was updated successfully, but these errors were encountered: