Before dropping the V1, please make sure V2 have builds working, since I
recall an incident recently where V1 jobs were restored to unblock an oVirt
On Sun, Oct 28, 2018 at 10:59 AM Daniel Belenky <dbelenky(a)redhat.com> wrote:
The change was tested and deployed in another test.
ovirt-provider-ovn have STDCIV1 running side by side with STDCIV2 which
causes the same change to be enqueued twice upon merge.
Ehud, can you work with the maintainers and see what is the status of
their migration? do they still need STDCIV1 jobs?
On Sun, Oct 28, 2018 at 10:16 AM oVirt Jenkins <jenkins(a)ovirt.org> wrote:
> Change 95040,2 (ovirt-provider-ovn) is probably the reason behind recent
> test failures in the "ovirt-4.2" change queue and needs to be fixed.
> This change had been removed from the testing queue. Artifacts build from
> change will not be released until it is fixed.
> For further details about the change see:
> For failed test results see:
> Infra mailing list -- infra(a)ovirt.org
> To unsubscribe send an email to infra-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> List Archives:
Infra mailing list -- infra(a)ovirt.org
To unsubscribe send an email to infra-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
irc: eedri (on #tlv #rhev-dev #rhev-integ)