Open Stack

Thanks, I assumed that was a bug id even before starting to read below
"Here's why:".


On Thu, Jan 17, 2013 at 5:27 PM, Thierry Carrez <thierry at openstack.org>wrote:

> 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
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
*Intel SSG/SSD/SOTC/PRC/CITT*
880 Zixing Road, Zizhu Science Park, Minhang District, Shanghai, 200241,
China
+862161166500
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130117/57abae7b/attachment.html>