Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On 07/11/2013 01:37 PM, Nachi Ueno wrote: 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. Great. I think the foc

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

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 : > Sean Dague wrote: >> On 07/11/2013 11

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

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 coupl

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

John Griffith wrote: > 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. There is someone assigned to it since it was raised at the release meeting. He doesn't se

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On 07/11/2013 11:54 AM, Sean Dague wrote: On 07/11/2013 11:33 AM, Matthew Treinish wrote: On Thu, Jul 11, 2013 at 08:16:26AM -0700, Dan Smith 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

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On Thu, Jul 11, 2013 at 9:38 AM, Russell Bryant wrote: > On 07/11/2013 11:28 AM, John Griffith wrote: > > > > > > > > On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith > > wrote: > > > > > In the corner to my left, our current largest gate reset culprit > > > appears

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On 07/11/2013 11:33 AM, Matthew Treinish wrote: On Thu, Jul 11, 2013 at 08:16:26AM -0700, Dan Smith 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/)

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On 07/11/2013 11:46 AM, Mark McLoughlin wrote: > On Thu, 2013-07-11 at 09:28 -0600, John Griffith wrote: >> On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith wrote: >> In the corner to my left, our current largest gate reset culprit appears to be neutron bug #1194026 - weighing in with 62 reche

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On Jul 11, 2013, at 8:28 AM, John Griffith wrote: > > > > On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith 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.

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On Thu, 2013-07-11 at 09:28 -0600, John Griffith wrote: > On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith 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.opensta

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On 07/11/2013 11:28 AM, John Griffith wrote: > > > > On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith > 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

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On Thu, Jul 11, 2013 at 08:16:26AM -0700, Dan Smith 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 o

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith 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

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

> 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 H

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

It's been set to 'High' now. Unfortunately I cannot give this bug the attention it deserves now, so I've not taken it. Adding quantum/neutron-core to trigger attention of other core devs. On 9 July 2013 19:40, Sean Dague wrote: > On 07/09/2013 12:20 PM, Thierry Carrez wrote: > >> Monty Taylor

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On 07/09/2013 12:20 PM, Thierry Carrez wrote: Monty Taylor wrote: I think having an uber-triager group comprised of the small set of gate watchers is not a terrible idea. Have the group, have that group be a member of all the other driver groups. FWIW you actually just need to be a bug supervi

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

Monty Taylor wrote: > I think having an uber-triager group comprised of the small set of gate > watchers is not a terrible idea. Have the group, have that group be a > member of all the other driver groups. FWIW you actually just need to be a bug supervisor to set priority, which in most cases mea

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

Sean Dague 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/) > > It has yet to be triaged by the neutron team, so is still sitting with > undefined

Re: [openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

On 07/09/2013 11:41 AM, Sean Dague 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/) > > It has yet to be triaged by the neutron team, so is still

[openstack-dev] Current biggest OpenStack gate fail culprit - neutron bug #1194026

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/) It has yet to be triaged by the neutron team, so is still sitting with undefined priority. However this see