<div dir="ltr"><div>Hi.</div><div>This is going to be embarrassing, but in my opinion it's better to be embarrassed and corrected than stay in error.</div><div><br></div><div>What is the preferred way of stating the reason for a recheck? I've kind of assumed that it's something like writing:</div><div><br></div><div>" recheck: this is broken" <br></div><div><br></div><div>but that doesn't trigger the CI. I've tried looking it up in the Zuul and Opendev docs, but couldn't find anything. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 28, 2022 at 1:02 PM Slawek Kaplonski <<a href="mailto:skaplons@redhat.com">skaplons@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">



<div><p style="margin:0px">Hi,</p>
<br><p style="margin:0px">Here are fresh data about bare rechecks.</p>
<br><p style="margin:0px"><span style="background-color:rgb(255,255,255)"><span style="font-family:monospace"><span style="color:rgb(0,0,0)">+--------------------+---------------+--------------+-------------------+ </span></span></span><br>| Team               | Bare rechecks | All Rechecks | Bare rechecks [%] | <br>+--------------------+---------------+--------------+-------------------+ <br>| requirements       | 2             | 2            | 100.0             | <br>| keystone           | 1             | 1            | 100.0             | <br>| OpenStackSDK       | 3             | 3            | 100.0             | <br>| tacker             | 3             | 3            | 100.0             | <br>| freezer            | 1             | 1            | 100.0             | <br>| rally              | 1             | 1            | 100.0             | <br>| OpenStack-Helm     | 14            | 15           | 93.33             | <br>| cinder             | 6             | 7            | 85.71             | <br>| kolla              | 20            | 25           | 80.0              | <br>| neutron            | 4             | 5            | 80.0              | <br>| Puppet OpenStack   | 10            | 13           | 76.92             | <br>| OpenStack Charms   | 3             | 6            | 50.0              | <br>| nova               | 11            | 22           | 50.0              | <br>| tripleo            | 8             | 19           | 42.11             | <br>| ironic             | 1             | 3            | 33.33             | <br>| Quality Assurance  | 1             | 3            | 33.33             | <br>| octavia            | 0             | 1            | 0.0               | <br>| OpenStackAnsible   | 0             | 1            | 0.0               | <br>| designate          | 0             | 1            | 0.0               | <br>| Release Management | 0             | 1            | 0.0               | <br>| horizon            | 0             | 1            | 0.0               | <br>+--------------------+---------------+--------------+-------------------+<br><br>Those data should be more accurate as my script now counts only comments from last 7 days, not all comments from patches updated in last 7 days.</p>
<br><p style="margin:0px">Reminder: "bare rechecks" are recheck comments without any reason given. If You need to do recheck for patch due to failed job(s), please first check such failed job and try to identify what was the issue there. Maybe there is already opened bug for that or maybe You can open new one and add it as explanation in the recheck comment. Or maybe it was some infra issue, in such case short explanation in the comment would also be enough.</p>
<br><p style="margin:0px">-- </p>
<p style="margin:0px">Slawek Kaplonski</p>
<p style="margin:0px">Principal Software Engineer</p>
<p style="margin:0px">Red Hat</p>
</div>
</blockquote></div>