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

Tox 2.3.1 was released on pypi a few minutes ago, and it fixes this issue. Jordan On Mon, Dec 14, 2015 at 12:55 AM, Robert Collins wrote: > On 13 December 2015 at 03:20, Yuriy Taraday wrote: > > Tempest jobs in all our projects seem to become

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

On 2015-12-14 12:18:07 +0100 (+0100), Jordan Pittier wrote: > Tox 2.3.1 was released on pypi a few minutes ago, and it fixes > this issue. Thanks for testing it--I've gone ahead and unblocked our image update automation. If anyone notices new abnormalities from tox, please let the Infra team

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

On 2015-12-14 12:55:45 +1300 (+1300), Robert Collins wrote: [...] > my suggestion would be that we either make tox pip installed > during jobs (across the board), so that we can in fact control it > with upper-constraints, That's a lot of added complication to deal with possible regressions in

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

On Sun, Dec 13, 2015 at 12:14 PM Shinobu Kinjo wrote: > What is the current status of this failure? > > > 2015-12-13 08:55:04.863 | ValueError: need more than 1 value to unpack > It shouldn't reappear in gate because CI images have been reverted to tox 2.2.1. It can be

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

What is the current status of this failure? > 2015-12-13 08:55:04.863 | ValueError: need more than 1 value to unpack Thank you Shinobu On Sun, Dec 13, 2015 at 4:48 AM, Yuriy Taraday wrote: > On Sat, Dec 12, 2015 at 10:27 PM Jeremy Stanley wrote: > >>

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

Thank you for your confirmation. Something installed tox onto my CentOS7, 3.10.0-229.el7.x86_64 because of dependency. I need to elaborate more. Shinobu On Sun, Dec 13, 2015 at 6:47 PM, Yuriy Taraday wrote: > On Sun, Dec 13, 2015 at 12:14 PM Shinobu Kinjo

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

On 13 December 2015 at 03:20, 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

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

On 2015-12-12 14:20:29 + (+), 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

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

On 2015-12-12 16:51:09 + (+), 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

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

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

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

Good initiative, will have to get infra folks and lifeless to chime in. For now we need devstack cores help with merging possibly https://review.openstack.org/#/c/256620/ -- dims > On Dec 12, 2015, at 4:20 PM, Yuriy Taraday wrote: > > Tempest jobs in all our projects

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

Awesome thanks so much Jeremy for tracking this down. -- Dims On Sat, Dec 12, 2015 at 9:55 PM, Jeremy Stanley wrote: > On 2015-12-12 21:18:29 +0300 (+0300), Davanum Srinivas wrote: >> Here's a really recent failure : >>

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

Hi, Jeremy. On Sat, Dec 12, 2015 at 8:27 PM Jeremy Stanley wrote: > On 2015-12-12 16:51:09 + (+), 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

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

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

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

On Sat, Dec 12, 2015 at 10:27 PM Jeremy Stanley wrote: > On 2015-12-12 19:00:23 + (+), Yuriy Taraday wrote: > > 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 > >

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

On 2015-12-12 21:18:29 +0300 (+0300), Davanum Srinivas wrote: > 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 - >

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

On 2015-12-12 19:00:23 + (+), Yuriy Taraday wrote: > 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 > upper-constraints.