<html><body>
<h3>Allon Mureinik created OVIRT-1752:</h3>
<pre> Summary: oVirt Engine CI failures on FC26
Key: OVIRT-1752
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1752
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: oVirt CI
Reporter: Allon Mureinik
Assignee: infra</pre>
<p>Hi Infra,</p>
<p>I've observed failures in oVirt Engine's CI on FC26, e.g. (<a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc26-x86_64/121/">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc26-x86_64/121/</a> – it's a manual trigger, but the same errors happen in the “real” CI).</p>
<p>The failure seems to be around collecting FindBugs exported artifacts: 05:49:40 [ovirt-engine_master_check-patch-fc26-x86_64] $ /bin/bash -xe /tmp/CommandInterpreterCondition8737185823553801263.sh 05:49:40 + find exported-artifacts/find-bugs/ -name ‘*.xml’ 05:49:40 + grep -e ‘.*’ 05:49:40 find: ‘exported-artifacts/find-bugs/’: No such file or directory 05:49:40 Run condition [Execute Shell] preventing perform for step [[Publish FindBugs analysis results]]</p>
<p>Which should only happen on EL7 according to automation/check-patch.sh Is checking `$STD_CI_DISTRO` there the wrong thing to do?</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzYS3r1Q939T2sgz150pnrffxs3pWNGu6ikARVfL-2F1YEmvL11d6NMSTZIqYwUba7T5xPEeS5YkzlOsG5wS4fGlP0fsp7ko2miCAB9RxElthJJKOnr2M6jTMy8oQjU9E63XC078UdN-2B-2FrBl4VBtKqy-2FEPjGmQF9EpTvmfG76xIxwrcIJyttES0ZMlO-2FHziE0HTLGjYIZ2BpZLd02-2Fg-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>