[ https://ovirt-jira.atlassian.net/browse/OVIRT-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35323#comment-35323 ]
The issue you've referred to is not that cause for the job to fail. What you've seen here: {code:java} 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]] {code} is a condition check, if the find command returns with false (ie nothing was found) it skips the publish.
From the log of the job you've attached, I see that the real failure might becaused by:
{code:java} 05:49:19 + su -l postgres -c ' /usr/bin/initdb --pgdata='\''/var/lib/pgsql/data'\'' --auth='\''ident'\''' 05:49:19 -bash: /usr/bin/initdb: No such file or directory 05:49:19 + cleanup 05:49:19 + su -l postgres -c ' /usr/bin/pg_ctl stop -D ‘\''/var/lib/pgsql/data'\’' -s -m fast' 05:49:19 -bash: /usr/bin/pg_ctl: No such file or directory 05:49:19 Took 0 seconds {code}
I'm closing the ticket as it's not an infra issue
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: infraHi Infra, I've observed failures in oVirt Engine's CI on FC26, e.g. (http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc26-x86_64/121/ – it's a manual trigger, but the same errors happen in the “real” CI). 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]] Which should only happen on EL7 according to automation/check-patch.sh Is checking `$STD_CI_DISTRO` there the wrong thing to do?
— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)