<div dir="ltr"><div>James,<br><br>What about blueprint patches? Is there a separate syntax or should we just use "recheck no bug"?<br><br></div>Thanks<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Jan 17, 2013 at 2:54 AM, James E. Blair <span dir="ltr"><<a href="mailto:jeblair@openstack.org" target="_blank">jeblair@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
The really short version of this is:<br>
<br>
* Start using bug numbers after rechecks or reverifies, like:<br>
"recheck bug #####"<br>
"reverify bug #####"<br>
* Use <a href="http://status.openstack.org/rechecks/" target="_blank">http://status.openstack.org/rechecks/</a> to find likely bugs<br>
<br>
Here's why:<br>
<br>
We run a lot of jobs in Jenkins. Between 1000 and 4000 per day. That<br>
presents a lot of opportunities for non-deterministic code (in programs<br>
or in tests) to show itself. And the fact that we gate changes on many<br>
of those jobs means we notice it when that happens.<br>
<br>
Sometimes a nondeterministic bug is rare, such that it doesn't really<br>
bother anyone and it won't be seen on a subsequent recheck. In that<br>
case, we've lost an opportunity to collect data on a real-world bug.<br>
Other times it happens so often that it affects nearly everyone in the<br>
project, and we need to mobilize to find and fix the bug ASAP.<br>
<br>
This change is designed to help collect information that can be used to<br>
help identify bugs that are affecting people the most, and communicate<br>
that as quickly as possible to everyone affected.<br>
<br>
Every time a recheck/reverify comment is left with a bug number<br>
attached, this page:<br>
<br>
<a href="http://status.openstack.org/rechecks/" target="_blank">http://status.openstack.org/rechecks/</a><br>
<br>
will update. It includes information such as when the bug was first and<br>
most recently seen, how many times it has prompted someone to recheck a<br>
change, what projects it has affected, and what changes in Gerrit it has<br>
affected.<br>
<br>
That page can be used by people working to fix bugs to help prioritize<br>
work. It is sorted by frecency[1], meaning that new bugs or high-impact<br>
bugs bubble up to the top, so if your change fails a test, you can look<br>
at that page and easily see if it already lists a likely cause.<br>
<br>
If you don't see a bug on that page, please go to Launchpad to search<br>
for an existing bug to use for the recheck, and if you don't find one,<br>
please file a new bug. Be sure to include some key output from the logs<br>
so that others who see the same bug will be able to identify it. Try to<br>
file the bug against the right project, but also remember that it's easy<br>
to add multiple projects in Launchpad and add or remove them later as<br>
needed.<br>
<br>
If the problem relates to infrastructure, such as a Jenkins exception,<br>
inability to download something from the network, etc, please file it<br>
against the openstack-ci project.<br>
<br>
There are times when it makes sense to recheck a change without a bug:<br>
for instance, if you know the branch or some dependency has changed<br>
since the last check, or you have just made a draft change visible. In<br>
those cases, you can leave a comment with the syntax "recheck no bug" or<br>
"reverify no bug". Please only do this if there really is no bug --<br>
that's what you're asserting to other developers when you leave such a<br>
comment.<br>
<br>
The new syntax is currently recognized by zuul, and the recheck status<br>
page is being updated. Starting soon, the comments from Jenkins that<br>
are left in Gerrit will include a link to this wiki page:<br>
<br>
<a href="http://wiki.openstack.org/GerritJenkinsGithub#Test_Failures" target="_blank">http://wiki.openstack.org/GerritJenkinsGithub#Test_Failures</a><br>
<br>
which contains a summary of this information and a reference for the new<br>
syntax, so it will be easily accessible in the future if you need to<br>
reference it. Starting in a week, the new syntax will be required.<br>
<br>
I hope the new system proves useful, and thanks for your help!<br>
<br>
[1] <a href="http://en.wiktionary.org/wiki/frecency" target="_blank">http://en.wiktionary.org/wiki/frecency</a><br>
<br>
-Jim<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div><b>Intel SSG/SSD/SOTC/PRC/CITT</b></div>
<div>880 Zixing Road, Zizhu Science Park, Minhang District, Shanghai, 200241,
China<br></div>
<div>+862161166500</div>
</div>