22 Aug
2017
22 Aug
'17
9:07 a.m.
On 22 August 2017 at 09:58, Michal Skrivanek <michal.skrivanek@redhat.com> wrote:
This seems unrelated to both changes mentioned below Please take a look at why does it identify those patches At least one issue seems to be http://lists.ovirt.org/pipermail/devel/2017-August/031057.html
It identified them because a test running just them + the "tested" repo failed. But this time it appears that the "tested" repo itself is broken and its currently causes all changes to be marked as broken. It looks like is was changed manually somehow. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted