[openstack-dev] Retiring "reverify no bug"

James E. Blair jeblair at openstack.org
Mon Dec 9 18:49:29 UTC 2013


On Wednesday December 11, 2013 we will remove the ability to use
"reverify no bug" to re-trigger gate runs for changes that have failed

This was previously discussed[1] on this list.  There are a few key
things to keep in mind:

* This only applies to "reverify", not "recheck".  That is, it only
  affects the gate pipeline, not the check pipeline.  You can still use
  "recheck no bug" to make sure that your patch still works.

* Core reviewers can still resubmit a change to the queue by leaving
  another "Approved" vote.  Please don't abuse this to bypass the intent
  of this change: to help identify and close gate-blocking bugs.

* You may still use "reverify bug #" to re-enqueue if there is a bug
  report for a failure, and of course you are encouraged to file a bug
  report if there is not.  Elastic-recheck is doing a great job of
  indicating which bugs might have caused a failure.

As discussed in the previous thread, the goal is to prevent new
transient bugs from landing in code by ensuring that if a change fails a
gate test that it is because of a known bug, and not because it's
actually introducing a bug, so please do your part to help in this

[1] http://lists.openstack.org/pipermail/openstack-dev/2013-November/020280.html


More information about the OpenStack-dev mailing list