Jeremy, Here's a really recent failure : http://logs.openstack.org/30/256130/5/check/gate-tempest-dsvm-neutron-src-taskflow/5845dd4/logs/devstacklog.txt.gz tox still is 2.3.0 - http://logs.openstack.org/30/256130/5/check/gate-tempest-dsvm-neutron-src-taskflow/5845dd4/logs/pip-freeze.txt.gz
Thanks, Dims On Sat, Dec 12, 2015 at 8:26 PM, Jeremy Stanley <fu...@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. 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. For the > benefit of people running DevStack themselves downstream, Ryan's > https://review.openstack.org/256620 looks like a more sensible > temporary workaround. > -- > Jeremy Stanley > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev