On 2015-12-12 14:20:29 +0000 (+0000), Yuriy Taraday wrote: > Tempest jobs in all our projects seem to become broken after tox 2.3.0 > release yesterday. It's a regression in tox itself: > https://bitbucket.org/hpk42/tox/issues/294 > > I suggest us to add tox to upper-constraints to avoid this breakage for now > and in the future: https://review.openstack.org/256947
See my review comment, but this won't help. > Note that we install tox in gate with no regard to global-requirements, so > only upper-constraints can save us from tox releases. No, it won't, since upper-constraints is merely used to constrain requirements lists. -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
