On Jul 11, 2013, at 8:28 AM, John Griffith <[email protected]> wrote:
> > > > On Thu, Jul 11, 2013 at 9:16 AM, Dan Smith <[email protected]> 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? +1 > > impact is currently overshadowing the potential for regression > detection, given the relatively small amount of coverage. Is this > something people would consider? > > Of course, the other option is to try to skip the offending test if > we're running with neutron support, which may help. Since we don't know > what the problem is and it *seems* to be an issue with resources not > becoming available before a timeout (AIUI), I worry that this will just > move the problem elsewhere. > This would be a lot better if that's possible. But if not, disable the whole thing. It's definitely a huge waste of resources to run a bunch of tests that fail repeatedly and cause us to have to re-check and use even more resources. I don't really like waiting 10 hours for patches to merge. - Chris
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
