On 2017-08-30 08:33:09 -0400 (-0400), Paul Belanger wrote: [...] > Regarding Bug 1713832 - Object PUT failed for > zaqar_subscription[1], which was reverted last night. That is a > great example to showcase elastic-recheck, basically if you look > back at the logstash queries, you can see the signs pointing to an > issue, but unfortunatly wasn't picked up until yesterday. > > The info above from Bogdan is great, the general idea is, if a job > fails in the check pipeline and elastic-recheck doesn't leave a > comment, it is likely a new failure. Moving forward, we need to > keep the blind rechecks to a minimum, as each time we do so, we > have the potential for breaking the gate down the road. [...]
And while it doesn't seem to have been exactly the case for this one, we've seen plenty of examples in the past where people (on various teams) have blindly rechecked a failing change to get it to merge... and then when you later classify the bug and track it back you find that it hit several times in the check pipeline on the very change which introduced the problem to begin with. Point being if you recheck without knowing why/what broke, it's increasingly likely you'll break things for everyone else too and turn a few moments of inconvenience for yourself into a week or more of pain for many others. -- Jeremy Stanley
signature.asc
Description: Digital signature
__________________________________________________________________________ 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
