| @vlotorev:matrix.org | Hi, tox 4 changed the way it collects environments to run. If no 'envlist' is specified in tox.ini then running 'tox' or 'tox run' will run empty 'py' envronment: | 22:38 |
|---|---|---|
| ``` | ||
| py: OK (0.32 seconds) | ||
| congratulations :) (0.45 seconds) | ||
| ``` | ||
| 'tox' job from zuul-jobs runs 'tox --notest' which creates that empty 'py' environment, then job runs 'tox --showconfig' and finds all environments in tox.ini and starts installing siblings but fails as only 'py' environment is created. | ||
| I found that zuul/zuul and zuul/zuul-jobs do have 'envlist' in tox.ini, so this issue is not applicable. | ||
| My proposal is to document the 'tox' job that is requires 'envlist' in tox.ini. | ||
| @vlotorev:matrix.org | * Hi, tox 4 changed the way it collects environments to run. If no 'envlist' is specified in tox.ini then running 'tox' or 'tox run' will run empty 'py' envronment: | 22:38 |
| ``` | ||
| py: OK (0.32 seconds) | ||
| congratulations :) (0.45 seconds) | ||
| ``` | ||
| 'tox' job from zuul-jobs runs 'tox --notest' which creates that empty 'py' environment, then job runs 'tox --showconfig' and finds all environments in tox.ini and starts installing siblings but fails as only 'py' environment was previously created. | ||
| I found that zuul/zuul and zuul/zuul-jobs do have 'envlist' in tox.ini, so this issue is not applicable. | ||
| My proposal is to document the 'tox' job that is requires 'envlist' in tox.ini. | ||
| @vlotorev:matrix.org | * Hi, tox 4 changed the way it collects environments to run. If no 'envlist' is specified in tox.ini then running 'tox' or 'tox run' will run empty 'py' envronment: | 22:44 |
| ``` | ||
| py: OK (0.32 seconds) | ||
| congratulations :) (0.45 seconds) | ||
| ``` | ||
| So lets a tox project has tox.ini without 'envlist' and 'tox' job from zuul-jobs is run for the project: | ||
| * 'tox' job runs 'tox --notest' which creates that empty 'py' environment, | ||
| * job runs 'tox --showconfig' and finds all environments in tox.ini | ||
| * job starts installing siblings but fails as only 'py' environment was previously created. | ||
| I found that zuul/zuul and zuul/zuul-jobs do have 'envlist' in tox.ini, so this issue is not reproducible. | ||
| My proposal is to document the 'tox' job that is requires 'envlist' in tox.ini (if I got it right what is going on). | ||
| @vlotorev:matrix.org | * Hi, tox 4 changed the way it collects environments to run. If no 'envlist' is specified in tox.ini then running 'tox' or 'tox run' will run empty 'py' envronment: | 22:45 |
| ``` | ||
| py: OK (0.32 seconds) | ||
| congratulations :) (0.45 seconds) | ||
| ``` | ||
| So lets a tox project has tox.ini without 'envlist' and 'tox' job from zuul-jobs is run for the project ('tox_envlist' job argument is empty): | ||
| - 'tox' job runs 'tox --notest' which creates that empty 'py' environment, | ||
| - job runs 'tox --showconfig' and finds all environments in tox.ini | ||
| - job starts installing siblings but fails as only 'py' environment was previously created. | ||
| I found that zuul/zuul and zuul/zuul-jobs do have 'envlist' in tox.ini, so this issue is not reproducible. | ||
| My proposal is to document the 'tox' job that is requires 'envlist' in tox.ini (if I got it right what is going on). | ||
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!