[ci][all]tox.tox_env.python.api.NoInterpreter - gate is blocked
Hi,
It seems that all the tox based jobs are blocked right now on master with the following error:
tox.tox_env.python.api.NoInterpreter: could not find python interpreter matching any of the specs
It is due to a recent bugfix in tox that uncovered another bug[1]. There is a fix proposed in tox [2].
[1]https://github.com/tox-dev/tox/issues/2811 [2]https://github.com/tox-dev/tox/pull/2828
On Fri, Jan 6 2023 at 04:35:56 PM +00:00:00, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-01-06 16:03:52 +0100 (+0100), Balazs Gibizer wrote: [...]
There is a fix proposed in tox
[...]
Which is now merged, so should appear in the next release (barring any reverts).
The tox 4.6.2. contains that fix and it seems it fixed the issue in case of our unit test targets (e.g. 'py310') but I still see missing interpreter errors in nova's functional targets (e.g. 'functional-py310'). I tracked this down to a conflict the the basepython = python3 settings nova has and the generative env def. It seems this combination worked in tox 3 but not in tox 4 so I opened a tox issues[1]. I have a temporary fix proposed in nova[2]
[1] https://github.com/tox-dev/tox/issues/2838 [2] https://review.opendev.org/c/openstack/nova/+/869545
-- Jeremy Stanley
participants (3)
-
Balazs Gibizer
-
Balazs Gibizer
-
Jeremy Stanley