-
-
Notifications
You must be signed in to change notification settings - Fork 521
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
WinError 1 Incorrect function when creating env on shared drive #1706
Comments
@jaraco , can you try using If it fails, then virtualenv has a bug, but tox could also use a relative path instead of the absolute UNC path. This might be hard to solve in tox v3 because tox uses the deprecated If virtualenv works well with UNC paths, tox could be giving it the wrong UNC path, perhaps with wrong escaping. |
Can you modify |
Sure. BTW, it's not necessary to modify tox.ini, but just also set TOX_PASSENV:
|
Indeed, if I try to create a symlink on the local (mounted) filesystem, it fails with the sam eerror:
|
Probably, because this file system is a SMB-mounted AFS file system, it can't store a Windows symlink, which relies on NTFS. Yet, we see:
So it seems that the symlink detection may not be effectively checking that symlinks work on the filesystem where the symlink will be created. |
When I am able to create the virtualenv by invoking virtualenv manually, virtualenv never attempts to link the dll:
|
I tried working around the issue by specifying a different directory for tox to create its environments. Since I don't know the difference between a tox work dir and a tox environments working dir, I set both:
Edit: Oh, as I repeatedly forget, those environment variables are injected, not respected. |
You're not invoking the same command. In the second case you're creating a virtual environment for Python 3.9, not Python 3.5, pass |
Indeed, but that's a virtualenv issue, not tox one. |
Good insight, and I agree. After replicating the issue by using |
I'm attempting to build a project on my Windows VM mounted against the source on my macOS host, but when I do, the env fails to be created:
I am, however, able to create the venv manually.
It seems something about how tox is attempting to create the virtualenv is triggering the failure.
Verbose:
The text was updated successfully, but these errors were encountered: