On 26/09/13 16:49, Sean Dague wrote:
As many folks know, gerrit takes comments of either the form
recheck bug #XXXXX
or
recheck no bug
To kick off the check queue jobs again to handle flakey tests.
The problem is that we're getting a lot more "no bug" than bugs at this
point. If a failure happens in the OpenStack gate, it's usually an
actual OpenStack race somewhere. Figuring out what the top races are is
*really* important to actually fixing those races, as it gives us focus
on what the top issues are in OpenStack that we need to fix. That makes
the gate good for everyone, and means less time babysitting your patches
through merge.
Now that Matt, Joe, and Clark have built the elastic-recheck bot, you
will often be given a hint in your review about the most probably race
that it was found. Please confirm the bug looks right before rechecking
with it, but it should help expedite finding the right issue.
http://status.openstack.org/rechecks/ is also helpful in seeing what's
most recently been causing issues.
Can I suggest including this link in Jenkins's comments on Gerrit? As
things stand it is two clicks away and the link is buried in the middle
of some very dense text. I know that for me personally this renders
"recheck no bug" more tempting than it should be ;)
cheers,
Zane.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
