-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Facing an invocation error through tox command #1600
Comments
For the one saying interpreter not found you can try setting in your tox.ini https://tox.readthedocs.io/en/latest/config.html#conf-skip_missing_interpreters to true. For the ones complaining about could not install we would need to see more information, try running it via |
Okay so I just did the skip missing interpreters part and that worked fine but the main issue I am facing is when I try to install the deps. Would you want me to put the entire error message after I do the |
Yes. But make it |
Okay so the error is:
|
Please use isolated builds, as described in https://tox.readthedocs.io/en/latest/example/package.html?highlight=isolated%20build#setuptools |
Okay so I did create a separate pyproject.toml file and made the change in the tox.ini file as well but there's still no change in the error for installing the deps. The pyproject.toml file:
The tox.ini file:
What if the error is fixed but stored as cache, just a guess? |
There should be change, can you post again the output? What tox version are you using? |
I am using the Tox version, 3.15.1. The output shows as:
|
There's something broken with the virtualenv alongside tox. Can you try to reinstall tox with |
Yeah I did both of those commands, it doesn't change anything. I restarted the IDE, checked the PATH variables for Python and even cloned the repo again to see if there was any change. |
The underlying issues seem to be a virtualenv bug; there is a pip has no dist-info within... I'm fairly certain that pypa/virtualenv#1841 will fix this, but that's probably a week away from release. |
Oh okay thank you, will keep a lookout for it. |
We have been getting InvocationErrors often on Arrow's CI pipeline runs with pypy3/tox/pytest on Windows over the past few days. I have attached the logs from our latest failure (and added a quick snippet):
3_windows-latest (pypy3).txt This is our tox.ini config and we have not changed much in it the past few weeks. |
@jadchaar feels to me like a pytest issue. pypa/virtualenv#1841 is unrelated. |
So I just ran the tox command in the project folder and once I did I got a lot of invocation errors, and I wasn't sure on how to fix it. This error was produced through the
tox -rvv
.Any help would be appreciated.
The text was updated successfully, but these errors were encountered: