-
-
Notifications
You must be signed in to change notification settings - Fork 529
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
Tox fails to run if the total directory path exceeds 80 characters. #649
Comments
Yes I encoutered this limitation as well, but I think there's nothing tox can do. It's a system issue (with shebang length limit) or a setuptools and distlib issue (with the way it install packages / entry points). The only workaround is to avoid too deep directory tree :/ Edit: there are other workarounds: pypa/pip#1773 (comment), also calling pip with |
In this case I think it would be helpful if we identified the problem at the beginning of test suite execution, printed a meaningful error message explaining the limitations, and stopped the execution. |
Some kind of sanity check for all theses problems at the beginning of a tox run would definitely be helpful. There are quite a few of these things, which are not really tox bugs as such, but due to upstream problems or OS specific limitations. |
The problem with "up-front" checks is that they are conditional
and expressing the conditions can be tricky and possibly needs to
be maintained. In principle there are things that tox
might do like these:
- try to minimize the length of what it adds to the path
- try to (optionally) use a global tmp directory with
a hashed/unique component added.
my 2cent
h
|
For anyone using Jenkins pipeline, it will surely be over 80 chars for the base-path and there's not much we can do about that. |
This should now be fixed via #935 |
BUG:
OS: Ubuntu 14.04
Tox: 2.9.1
Pip: 9.0.1
Virtualenv: 15.1.0
Steps to reproduce:
Output:
Reducting the total path to directory containing
tox.ini
to 79 characters or less fixes the issue.Possibly related: #66
The text was updated successfully, but these errors were encountered: