<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 26, 2018 at 1:06 PM, 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div class="gmail-h5"><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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);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></span> </blockquote></div></div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div class="gmail-h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>
<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></div></div><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>
</blockquote></div><br></div><div class="gmail_extra">The build fails due to <span><a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc27-s390x/">vdsm_master_build-artifacts-fc27-s390x</a> , which is failing for some time now.<br></span></div><div class="gmail_extra"><span>Who can look into that?<br><br></span></div><div class="gmail_extra"><span>The lago VM crash is a secondary less urgent issues, although it will be nice if it can be investigated as well. Last time, it failed on a specific slave frequently (a non Centos one).<br><br></span></div><div class="gmail_extra"><span>Thanks,<br></span></div><div class="gmail_extra"><span>Edy.<br></span></div><div class="gmail_extra"><span><br></span></div></div>