-
-
Notifications
You must be signed in to change notification settings - Fork 509
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
Infinite loop over automatically provisioned requirement with unmatched environment marker #3136
Labels
help:wanted
Issues that have been acknowledged, a solution determined and a PR might likely be accepted.
Comments
I think that I may have hit this bug this morning, tox gets stuck for no clear reason:
Not sure what caused this regression, yesterday all was fine. Also dis a thread dump, it seems that it gets stuck anyway, not only on provisioning.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
help:wanted
Issues that have been acknowledged, a solution determined and a PR might likely be accepted.
Issue
When attempting to auto-provision a tox environment with an unmet requirement masked by an environment marker.
Environment
Provide at least:
Output of
pip list
of the host Python, wheretox
is installedOutput of running tox
Output of
tox -rvv
That's strange, because that's not the same error that occurs without
-rvv
.Output of
tox
Minimal example
It seems that the environment marker
python_version < "3.8"
is being used to filter the requirement for install but not for assessing the environment, so tox repeatedly thinks its requirements are unmet, installs them, and retries.I suspect what needs to happen is that tox needs to honor the environment markers when assessing the environment.
The text was updated successfully, but these errors were encountered: