-
Notifications
You must be signed in to change notification settings - Fork 22
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
24.7.2: Testing fails without the TOX_PACKAGE
environment variable
#110
Comments
If you are running those tests outside of Tox you'll have to set this environment variable to point at an Incremental dist that can be installed in the venv. Heads up: there may be some churn in this area when I address #109, so if you have to patch these tests to get them working in your environment you'll risk redoing that work soon. It might be better to skip these tests for now. |
Thanks for explanation. I never heard about the Some background: I'm running tests using |
Thank you, that background is very helpful! I hadn't heard of tox-current-env before. Its function is much like what I do in our CI workflow, where I build the package and then run the tests against it with Looking at your patches, I can't quite follow why 02-tox-enable-tests.patch is necessary. Can you not use an env named |
This is not related to Because of that I simply need the default tests available immediately and so the patch is needed. OTOH, it should be possible to specify the Python version using something like |
The |
Certainly! I mean they are isomorphic: both allow running the tests against a specific Incremental package. |
I tried setting |
@glaubitz How exactly? (I would also expect them to fail without Internet access.) |
When I run tests without the
TOX_PACKAGE
environment variable set then several tests fails:The text was updated successfully, but these errors were encountered: