[openstack-dev] [all] tox 2.3.0 broke tempest jobs

Yuriy Taraday yorik.sar at gmail.com
Sat Dec 12 19:00:23 UTC 2015

Hi, Jeremy.

On Sat, Dec 12, 2015 at 8:27 PM Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2015-12-12 16:51:09 +0000 (+0000), Jeremy Stanley wrote:
> [...]
> > No, it won't, since upper-constraints is merely used to constrain
> > requirements lists.
> I take that back, the pip_install function in DevStack applies
> upper-constraints.txt on anything it installs, but regardless it's
> misleading to try to pin it in upper-constraints.txt because that
> won't help any of the numerous other jobs which may use constraints
> but rely on preinstalled tox.

I think it should be a good first step in right direction. For example,
with today's issue it would break gate for tempest itself only since all
other jobs would have preinstalled tox reverted to one mentioned in

> Also I've confirmed that tempest jobs
> do still seem to be working fine in our CI, and don't seem to be
> unconditionally upgrading the preinstalled tox version.

Pip doesn't upgrade tox if it is already installed, but will obey
constraints if they're provided. That's why it works with current reverted

For the
> benefit of people running DevStack themselves downstream, Ryan's
> https://review.openstack.org/256620 looks like a more sensible
> temporary workaround.

Won't they use constraints too? I think we cover DevStack issue with
upper-constraints change as a more permanent solution.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151212/3985d1f1/attachment.html>

More information about the OpenStack-dev mailing list