[openstack-dev] [CI] Recheck/reverify syntax changing

Thierry Carrez thierry at openstack.org
Thu Jan 17 09:27:14 UTC 2013

Zhongyue Luo wrote:
> What about blueprint patches? Is there a separate syntax or should we
> just use "recheck no bug"?

When you say "recheck bug #####" the bug number you mention is not about
what the patch fixes, it's about the false negative in the test that
prevented the test from succeeding.

For example, you may have a simple typo fix, and the gate fails due to a
random test failure in LockUtilsTest... You should search for a bug
about that random test failure in LockUtilsTest (create it if it doesn't
exist) and reference *that* bug, not the original typo bug or any
blueprint, in your "recheck bug #####" command.

The whole idea is to track such false negatives issues and prioritize
them, rather than just say "reverify" and forget about them.

Thierry Carrez (ttx)
Release Manager, OpenStack

More information about the OpenStack-dev mailing list