The build-artifacts are the developer's responsibility and is not related to CQ. it does not actually matter though why the build-artifacts failed as there are passing builds after this failure which means the project would have a passing package to be tested by CQ which include the changes that came before it. We do not have a re-try on failures as it failed for a specific reason that needs to be looked at. you can look at the chart that I sent to the list and see that if build-artifacts fail I will check the status and if needed will alert the developer to look into it.
On Fri, Jun 21, 2019 at 12:01 AM Nir Soffer <nsof...@redhat.com> wrote: > On Wed, Jun 19, 2019 at 7:03 PM Dafna Ron <d...@redhat.com> wrote: > >> this was a failed build-artifacts. >> its now fixed as there are several passing builds after this one >> > > Why build-artifacts failed? > > Do we have a retry on failures? > > >> On Wed, Jun 19, 2019 at 3:16 AM oVirt Jenkins <jenk...@ovirt.org> wrote: >> >>> A system test invoked by the "ovirt-master" change queue including change >>> 100778,6 (vdsm) failed. However, this change seems not to be the root >>> cause for >>> this failure. Change 100783,7 (vdsm) that this change depends on or is >>> based >>> on, was detected as the cause of the testing failures. >>> >>> This change had been removed from the testing queue. Artifacts built >>> from this >>> change will not be released until either change 100783,7 (vdsm) is fixed >>> and >>> this change is updated to refer to or rebased on the fixed version, or >>> this >>> change is modified to no longer depend on it. >>> >>> For further details about the change see: >>> https://gerrit.ovirt.org/#/c/100778/6 >>> >>> For further details about the change that seems to be the root cause >>> behind the >>> testing failures see: >>> https://gerrit.ovirt.org/#/c/100783/7 >>> >>> For failed test results see: >>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14624/ >>> _______________________________________________ >>> Infra mailing list -- infra@ovirt.org >>> To unsubscribe send an email to infra-le...@ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CHXVUBUQZO3OS2OQ2FWEGSFB2KS7F33V/ >>> >> _______________________________________________ >> Infra mailing list -- infra@ovirt.org >> To unsubscribe send an email to infra-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FNSPEESXJOPRYBRKKABJ3PUGILZ2R53X/ >> >
_______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YUWHSZH7ZF5I5JIYKL25DITGDBHATR2R/
