-
-
Notifications
You must be signed in to change notification settings - Fork 528
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 2.3 regression #294
Comments
Original comment by jordan_pittier Quick tests of tox-2.3.1 looks good. I think it's fixed for OpenStack. |
Original comment by @hpk42 let me know if tox-2.3.1 is stable again. |
Original comment by @hpk42 fix issue294: re-allow cross-section substitution for setenv setting. → <> |
Original comment by bossylobster It broke us too: https://github.com/GoogleCloudPlatform/gcloud-python/blob/d6820b91788adcb11aee119349b1489123c12e9f/tox.ini#L56-L58 |
Original comment by @hpk42 "nobody is using that feature" is for some odd reason what i thought. sorry about that. will see to fix things and release a tox-2.3.1 early next week. please stick with tox-2.2 series for the time being. |
Original comment by @The-Compiler I've talked with @hpk42 about this already, and this is due to the recent changes breaking getting |
Hi,
At least two openstack project (Tempest and Nova) are hit by a regression introduced with Tox 2.3 released a couple of hours ago on pypi.
Here is a relevant stack trace:
I think Tox failed on these lines:
Full tox.ini here: https://github.com/openstack/tempest/blob/02ef4c2956318b09cc47506af2361ab3d8907a10/tox.ini
The text was updated successfully, but these errors were encountered: