Folks, I have been noticing that some of us use 'recheck' as a knee jerk reaction. Please STOP!
Please, take the time to look into the failure mode, see if there's a bug reported already, help the triage process, and ultimately, once you're sure that the issue is not introduced by your patch, consider to type 'recheck bug #####' mindfully. If the gate queue is hovering over at 400 jobs [0], we need to be conscious of the fact that the gate is busy and we should back off. Besides, there is no point in jamming stuff through the gate if there's a burning issue that needs to be flushed out. For checking gate instabilities, tools [1,2,3] are your friends. If you don't know how to use them, please reach out to me and I'll be happy to walk you through. Cheers, Armando [0] http://status.openstack.org/zuul/ [1] http://grafana.openstack.org/dashboard/db/neutron-failure-rate [2] http://status.openstack.org/openstack-health/#/g/project/openstack~2Fneutron [3] http://status.openstack.org/elastic-recheck/
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
