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
[BUG] venv provisioning seems to enter an infinite loop under Python 3.8 with virtualenv==20.0.1
when pip
is in requires
#1518
Comments
Weirdly, another job in the same CI run doesn't explode like that: https://github.com/ansible/ansible-lint/pull/637/checks?check_run_id=438702342 |
Hm... Looks like the common denominator is Python 3.8, other jobs seem to be unaffected. |
@gaborbernat any ideas? |
not at the moment 🤔 |
virtualenv==20.0.1
when pip
is in requires
virtualenv==20.0.1
when pip
is in requires
Is this still on with 20.0.3? |
I'll check. It seemed to only be reproducible in GH Actions Workflows. |
Alright, it doesn't crash anymore with Thanks, Bernát! |
CI log: https://github.com/ansible/ansible-lint/pull/637/checks?check_run_id=438702207#step:6:30
$ TOXENV=docs python -m tox --parallel auto --notest
$ python -m pip freeze --all
The text was updated successfully, but these errors were encountered: