Open Stack

Hi Sean

Sorry for it taking long time to fixing this problem.
At least, 3 neutron core dev is working on this issue, but
it is kind of timing issue so we are struggling to replicate it.

I'm also OK to move it for non-voting now.


2013/7/11 Thierry Carrez <thierry at openstack.org>:
> Sean Dague wrote:
>> On 07/11/2013 11:54 AM, Sean Dague wrote:
>>> Let's start with the test skip.
>>>
>>> I am however pretty frustrated that we're really not getting anyone from
>>> neutron looking at this. We're at 121 rechecks (plus I'm sure there were
>>> plenty of no bug rechecks, I've seen a couple). So 150+ gate resets
>>> because of this bug. Which is 150hrs worth of delay put into the gate.
>>
>> Actually, I'm revising my point of view. If we skip the test, people
>> can't debug in the gate. if we make the job non-voting, the neutron team
>> can submit patches up and run rechecks on them to try to reproduce the
>> fail.
>>
>> So let's go non-voting here.
>
> The problem with this approach is that you'll fail to notice OTHER
> (genuine) issues that your patch introduces, since you'll be trained to
> ignore that line (and not necessarily look into the details).
>
> Disabling only the flaky test sounds like a better way to go to me. Yes
> it makes fixing the flaky test slightly more difficult, but at least it
> doesn't increase the regression risk.
>
> --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev