Open Stack

On Thu, 2013-07-11 at 09:28 -0600, John Griffith wrote:
> On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith <dms at danplanet.com> wrote:
> 
> > > In the corner to my left, our current largest gate reset culprit
> > > appears to be neutron bug #1194026 - weighing in with 62 rechecks
> > > since June 24th (http://status.openstack.org/rechecks/)
> >
> > So, with some of the highest rates of patch traffic we've seen over the
> > last couple of weeks before the H2 deadline, I think this is really
> > becoming a problem. I think merge times are through the roof as a
> > result.
> >
> > Since the neutron gate is not a full tempest run, I think we should
> > consider making a temporary change. I know that turning it into a
> > non-voting job is not a popular solution, and I hate to even suggest
> > it. However, it's just a subset of the tests anyway and I think the
> >
> 
> Well to be blunt, if there's not even anybody assigned to the defect and
> it's significantly impacting
> the progress of every other project.  I don't know that it's such a bad
> idea.  The process worked, it
> identified an issue, now it's known/understood however it's causing
> significant turmoil everywhere else.
> Are we gaining anything by having it continue to fail and do rechecks for
> the next week?

I feel a similar way to this as I do about regressions for which we've
identified a root cause patch, even though it's a completely separate
thing. In those cases, we should take decisive action to revert quickly.

This is holding people up, there's level of failure is unacceptable,
continuing to frustrate people is not going to get it fixed faster. In
this case, we should take decisive action and make it non-voting
quickly.

Cheers,
Mark.