Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-14 Thread Neil Jerram
On 14/01/16 12:01, Davanum Srinivas wrote: > Neil, > > The global requirements upper-constraints.txt do not cover neutron > unit test targets. So the unit tests pick up latest from pypi. I'm afraid I don't understand how that's related to my question below. Could you explain further? It seems

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-14 Thread Davanum Srinivas
Neil, Apologies. you are right, test_bash_completion is a unit test. and neutron failure is in "gate-neutron-python27-constraints". so yes, that was broken by the change to upper-constraints.txt. https://review.openstack.org/#/c/266042/ is a valid request as it has a g-r change and a u-c change

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-14 Thread Neil Jerram
On 13/01/16 19:27, Carl Baldwin wrote: > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some time by the > upper-constraints.txt file. This is great progress and I applaud it. > I'll continue to cheer on this effort. >

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-14 Thread Davanum Srinivas
Neil, The global requirements upper-constraints.txt do not cover neutron unit test targets. So the unit tests pick up latest from pypi. -- Dims On Thu, Jan 14, 2016 at 6:51 AM, Neil Jerram wrote: > On 13/01/16 19:27, Carl Baldwin wrote: >> Hi, >> >> I was looking

[openstack-dev] Further closing the holes that let gate breakage happen

2016-01-13 Thread Carl Baldwin
Hi, I was looking at the most recent gate breakage in Neutron [1], fixed by [2]. This gate breakage was held off for some time by the upper-constraints.txt file. This is great progress and I applaud it. I'll continue to cheer on this effort. Now to the next problem. If my assessment of this

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-13 Thread Armando M.
On 13 January 2016 at 11:24, Carl Baldwin wrote: > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some time by the > upper-constraints.txt file. This is great progress and I applaud it. > I'll

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-13 Thread Sean Dague
On 01/13/2016 03:41 PM, Armando M. wrote: > > > On 13 January 2016 at 11:24, Carl Baldwin > wrote: > > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-13 Thread Robert Collins
On 14 January 2016 at 08:24, Carl Baldwin wrote: > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some time by the > upper-constraints.txt file. This is great progress and I applaud it. > I'll

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-13 Thread Jeremy Stanley
On 2016-01-14 12:32:02 +1300 (+1300), Robert Collins wrote: [...] > We tried to add some unit test jobs to cross check constraints, but we > need some infrastructure work to permit specifying that a unit test > job for a change to requirements checkout the code for e.g. nova and > run nova's