<div dir="ltr"><div><div>did you re-trigger the job? there are actually two failed aftifacts for that change. <br><br></div>The point is that if you fail even one of the build-artifacts jobs that CQ will not even start to run on your change since we expect the build-artifacts you selected for your project to pass. <br></div><div>I think that what Eyal meant on the check-patch job is that if you want to integrate a new distro you should probably stabilize it first and a good way of doing it is not to add it to your build-artifacts job bit treat it as an independent job that would be run on check-patch. <br></div><div>that way, you can find the failures on check-patch, and if you cannot fix them you can still decide to merge the patch and it would not to run CQ on your patch since the build-artifacts is not in your required artifacts list. <br><br></div><div><div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 26, 2018 at 11:06 AM, Edward Haas <span dir="ltr"><<a href="mailto:ehaas@redhat.com" target="_blank">ehaas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 26, 2018 at 12:16 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Sat, Feb 24, 2018 at 4:36 PM, oVirt Jenkins <<a href="mailto:jenkins@ovirt.org" target="_blank">jenkins@ovirt.org</a>> wrote:<br>
> Change 83979,8 (vdsm) is probably the reason behind recent system test failures<br>
> in the "ovirt-master" change queue and needs to be fixed.<br>
><br>
> This change had been removed from the testing queue. Artifacts build from this<br>
> change will not be released until it is fixed.<br>
><br>
> For further details about the change see:<br>
> <a href="https://gerrit.ovirt.org/#/c/83979/8" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/8<wbr>3979/8</a><br>
><br>
> For failed test results see:<br>
> <a href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5850/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/o<wbr>virt-master_change-queue-teste<wbr>r/5850/</a><br>
<br>
</span>I see that one of the network functional tests is failing<br>
build-artifacts and the release of this build.<br>
<br>
Edy, could you see why?<br>
<br>
<a href="http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/3226/artifact/exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.check-merged.sh/check-merged.sh.log" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/v<wbr>dsm_master_check-merged-el7-x8<wbr>6_64/3226/artifact/exported-ar<wbr>tifacts/mock_logs/mocker-epel-<wbr>7-x86_64.el7.check-merged.sh/<wbr>check-merged.sh.log</a><br>
</blockquote></div><br></div></span><div class="gmail_extra">The functional tests are running on a Lago VM, which crashed (the timeout kicked in).<br></div><div class="gmail_extra">But I do not see the relevance between the artifact build and the check-merge, the later is not a gateway to any automation step I know of at the moment (for good and for worse, mainly worse).<br><br></div></div>
<br>______________________________<wbr>_________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/infra</a><br>
<br></blockquote></div><br></div>