Re: [openstack-dev] [gate] large-ops failure spike

2016-01-21 Thread Roman Vasilets
>I also suggest their time has probably come and gone. There is no one >active on them, and the Rally team is. Fully agree with idea to use Rally for large-ops. It was build for testing OpenStack under the scale=) On Wed, Jan 20, 2016 at 9:08 PM, Tony Breeds wrote: >

Re: [openstack-dev] [gate] large-ops failure spike

2016-01-20 Thread Matthew Treinish
On Wed, Jan 20, 2016 at 07:45:16AM -0500, Sean Dague wrote: > The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in > the last 24 hours. > > http://tinyurl.com/j5u4nf5 > > There isn't an obvious culprit at this point. I spent some time this There is a very obvious culprit, pip 8

Re: [openstack-dev] [gate] large-ops failure spike

2016-01-20 Thread Sean Dague
On 01/20/2016 10:03 AM, Matthew Treinish wrote: > On Wed, Jan 20, 2016 at 07:45:16AM -0500, Sean Dague wrote: >> The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in >> the last 24 hours. >> >> http://tinyurl.com/j5u4nf5 >> >> There isn't an obvious culprit at this point. I spent

Re: [openstack-dev] [gate] large-ops failure spike

2016-01-20 Thread Tony Breeds
On Wed, Jan 20, 2016 at 07:45:16AM -0500, Sean Dague wrote: > The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in > the last 24 hours. > > http://tinyurl.com/j5u4nf5 > > There isn't an obvious culprit at this point. I spent some time this > morning digging into it a bit.

[openstack-dev] [gate] large-ops failure spike

2016-01-20 Thread Sean Dague
The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in the last 24 hours. http://tinyurl.com/j5u4nf5 There isn't an obvious culprit at this point. I spent some time this morning digging into it a bit. Possibly each individual instance build got slower, possibly some other timeout