Open Stack

Hi.
This is going to be embarrassing, but in my opinion it's better to be
embarrassed and corrected than stay in error.

What is the preferred way of stating the reason for a recheck? I've kind of
assumed that it's something like writing:

" recheck: this is broken"

but that doesn't trigger the CI. I've tried looking it up in the Zuul and
Opendev docs, but couldn't find anything.

On Thu, Jul 28, 2022 at 1:02 PM Slawek Kaplonski <skaplons at redhat.com>
wrote:

> Hi,
>
> Here are fresh data about bare rechecks.
>
> +--------------------+---------------+--------------+-------------------+
> | Team               | Bare rechecks | All Rechecks | Bare rechecks [%] |
> +--------------------+---------------+--------------+-------------------+
> | requirements       | 2             | 2            | 100.0             |
> | keystone           | 1             | 1            | 100.0             |
> | OpenStackSDK       | 3             | 3            | 100.0             |
> | tacker             | 3             | 3            | 100.0             |
> | freezer            | 1             | 1            | 100.0             |
> | rally              | 1             | 1            | 100.0             |
> | OpenStack-Helm     | 14            | 15           | 93.33             |
> | cinder             | 6             | 7            | 85.71             |
> | kolla              | 20            | 25           | 80.0              |
> | neutron            | 4             | 5            | 80.0              |
> | Puppet OpenStack   | 10            | 13           | 76.92             |
> | OpenStack Charms   | 3             | 6            | 50.0              |
> | nova               | 11            | 22           | 50.0              |
> | tripleo            | 8             | 19           | 42.11             |
> | ironic             | 1             | 3            | 33.33             |
> | Quality Assurance  | 1             | 3            | 33.33             |
> | octavia            | 0             | 1            | 0.0               |
> | OpenStackAnsible   | 0             | 1            | 0.0               |
> | designate          | 0             | 1            | 0.0               |
> | Release Management | 0             | 1            | 0.0               |
> | horizon            | 0             | 1            | 0.0               |
> +--------------------+---------------+--------------+-------------------+
>
> 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.
>
> 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.
>
> --
>
> Slawek Kaplonski
>
> Principal Software Engineer
>
> Red Hat
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220728/cedaf5bf/attachment.htm>