<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 19, 2016 at 10:30 AM, Eyal Edri <span dir="ltr"><<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">we have it for all versions:<div><a href="http://resources.ovirt.org/repos/ovirt/experimental/" target="_blank">http://resources.ovirt.org/repos/ovirt/experimental/</a></div></div></blockquote><div><br></div><div>So:</div><div><br></div><div><a href="http://resources.ovirt.org/repos/ovirt/experimental/3.6/latest.tested">http://resources.ovirt.org/repos/ovirt/experimental/3.6/latest.tested</a><br></div><div><a href="http://resources.ovirt.org/repos/ovirt/experimental/4.0/latest.tested">http://resources.ovirt.org/repos/ovirt/experimental/4.0/latest.tested</a><br></div><div><a href="http://resources.ovirt.org/repos/ovirt/experimental/master/latest.tested">http://resources.ovirt.org/repos/ovirt/experimental/master/latest.tested</a><br></div><div><br></div><div>should be equivalend to the snapshot + snapshot-static repos right?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div></div><div class=""><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 19, 2016 at 11:27 AM, Tolik Litovsky <span dir="ltr"><<a href="mailto:tlitovsk@redhat.com" target="_blank">tlitovsk@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Is it only for master job ? <div>Or we have such repos for all branches ?</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Jul 19, 2016 at 10:13 AM, Eyal Edri <span dir="ltr"><<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Ryan/Tolik,<div>Can you build appliance only from tested engine repo [1] ? lets see how it affects the stability, next step will be to publish tested appliance after it runs Lago verification.</div><div><br></div><div>[1] <a href="http://resources.ovirt.org/repos/ovirt/experimental/master/latest.tested/" target="_blank">http://resources.ovirt.org/repos/ovirt/experimental/master/latest.tested/</a> (published only after ovirt-system-tests basic suite finish successfully)</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 19, 2016 at 10:10 AM, Lev Veyde <span dir="ltr"><<a href="mailto:lveyde@redhat.com" target="_blank">lveyde@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div><div style="font-family:"times new roman","new york",times,serif;font-size:12pt;color:rgb(0,0,0)"><div>Hi Eyal,<br></div><div><br></div><div>The last failed run failed on: </div><div><span><b>15:50:02</b> </span>[ INFO ] Extracting disk image from OVF archive (could take a few minutes depending on archive size)</div><div><span><b>21:35:04</b> </span>Build timed out (after 360 minutes). Marking the build as failed.<br></div><div><br></div><div>So it basically got stuck while extracting the OVF image.<br></div><div><br></div><div>Some previous runs failed mostly on either:<br></div><div>a) broken ovirt-engine-appliance build<br></div><div>b) ovirt-engine-appliance missing from the yum repo<br></div><div><br></div><div>We need to make sure that the process of building and publishing the ovirt-engine-appliance works flawlessly e.g. build ovirt-engine, publish it into the repo so that the build of the appliance can work, then publish it to the repo as well.<br></div><div>This is extra important as the hosted-engine flow installation will probably become the default one, and without synced ovirt appliance we can't really test the changes in the engine.<br></div><div><br></div><div><span name="x"></span>Thanks in advance,<br>Lev Veyde.<span name="x"></span><br></div><div><br></div><hr><div style="color:rgb(0,0,0);font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b>"Eyal Edri" <<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>><br><b>To: </b><a href="mailto:jenkins@jenkins.phx.ovirt.org" target="_blank">jenkins@jenkins.phx.ovirt.org</a><br><b>Cc: </b>"infra" <<a href="mailto:infra@ovirt.org" target="_blank">infra@ovirt.org</a>>, "Lev Veyde" <<a href="mailto:lveyde@redhat.com" target="_blank">lveyde@redhat.com</a>>, <a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a><br><b>Sent: </b>Tuesday, July 19, 2016 8:26:22 AM<br><b>Subject: </b>Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #32<div><div><br><div><br></div><p dir="ltr">Lev, this test is a bit flaky going from stable to failure quite often, can you check what is causing it? </p>
<div class="gmail_quote">On Jul 19, 2016 12:35 AM, <<a href="mailto:jenkins@jenkins.phx.ovirt.org" target="_blank">jenkins@jenkins.phx.ovirt.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">See <<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/32/changes" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/32/changes</a>><br>
<br>
Changes:<br>
<br>
[Lev Veyde] ovirt-system-tests: Add automation for he_iscsi_basic_suite_4.0<br>
<br>
[Sandro Bonazzola] vdsm: avoid fc24 out of master<br>
<br>
[Sandro Bonazzola] ovirt-engine: add 3.6.8 branch testing<br>
<br>
------------------------------------------<br>
[...truncated 620 lines...]<br>
<br>
WORKSPACE="$PWD"<br>
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"<br>
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"<br>
<br>
rm -rf "$WORKSPACE/exported-artifacts"<br>
mkdir -p "$WORKSPACE/exported-artifacts"<br>
<br>
if [[ -d "$TESTS_LOGS" ]]; then<br>
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"<br>
fi<br>
<br>
[ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson1764906258788527221.sh<br>
+ echo shell_scripts/<a href="http://system_tests.collect_logs.sh" rel="noreferrer" target="_blank">system_tests.collect_logs.sh</a><br>
shell_scripts/<a href="http://system_tests.collect_logs.sh" rel="noreferrer" target="_blank">system_tests.collect_logs.sh</a><br>
+ VERSION=4.0<br>
+ SUITE_TYPE=<br>
+ WORKSPACE=<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/</a>><br>
+ OVIRT_SUITE=4.0<br>
+ TESTS_LOGS=<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/exported-artifacts" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/exported-artifacts</a>><br>
+ rm -rf <<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/32/artifact/exported-artifacts" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/32/artifact/exported-artifacts</a>><br>
+ mkdir -p <<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/32/artifact/exported-artifacts" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/32/artifact/exported-artifacts</a>><br>
+ [[ -d <<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/exported-artifacts" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/exported-artifacts</a>> ]]<br>
POST BUILD TASK : SUCCESS<br>
END OF POST BUILD TASK : 0<br>
Match found for :.* : True<br>
Logical operation result is TRUE<br>
Running script : #!/bin/bash -xe<br>
echo "shell-scripts/mock_cleanup.sh"<br>
<br>
shopt -s nullglob<br>
<br>
<br>
WORKSPACE="$PWD"<br>
<br>
# Make clear this is the cleanup, helps reading the jenkins logs<br>
cat <<EOC<br>
_______________________________________________________________________<br>
#######################################################################<br>
# #<br>
# CLEANUP #<br>
# #<br>
#######################################################################<br>
EOC<br>
<br>
<br>
# Archive the logs, we want them anyway<br>
logs=(<br>
./*log<br>
./*/logs<br>
)<br>
if [[ "$logs" ]]; then<br>
tar cvzf exported-artifacts/logs.tgz "${logs[@]}"<br>
rm -rf "${logs[@]}"<br>
fi<br>
<br>
# stop any processes running inside the chroot<br>
failed=false<br>
mock_confs=("$WORKSPACE"/*/mocker*)<br>
# Clean current jobs mockroot if any<br>
for mock_conf_file in "${mock_confs[@]}"; do<br>
[[ "$mock_conf_file" ]] || continue<br>
echo "Cleaning up mock $mock_conf"<br>
mock_root="${mock_conf_file##*/}"<br>
mock_root="${mock_root%.*}"<br>
my_mock="/usr/bin/mock"<br>
my_mock+=" --configdir=${mock_conf_file%/*}"<br>
my_mock+=" --root=${mock_root}"<br>
my_mock+=" --resultdir=$WORKSPACE"<br>
<br>
#TODO: investigate why mock --clean fails to umount certain dirs sometimes,<br>
#so we can use it instead of manually doing all this.<br>
echo "Killing all mock orphan processes, if any."<br>
$my_mock \<br>
--orphanskill \<br>
|| {<br>
echo "ERROR: Failed to kill orphans on $chroot."<br>
failed=true<br>
}<br>
<br>
mock_root="$(\<br>
grep \<br>
-Po "(?<=config_opts\['root'\] = ')[^']*" \<br>
"$mock_conf_file" \<br>
)" || :<br>
[[ "$mock_root" ]] || continue<br>
mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || :<br>
if [[ "$mounts" ]]; then<br>
echo "Found mounted dirs inside the chroot $chroot. Trying to umount."<br>
fi<br>
for mount in "${mounts[@]}"; do<br>
sudo umount --lazy "$mount" \<br>
|| {<br>
echo "ERROR: Failed to umount $mount."<br>
failed=true<br>
}<br>
done<br>
done<br>
<br>
# Clean any leftover chroot from other jobs<br>
for mock_root in /var/lib/mock/*; do<br>
this_chroot_failed=false<br>
mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || :<br>
if [[ "$mounts" ]]; then<br>
echo "Found mounted dirs inside the chroot $mock_root." \<br>
"Trying to umount."<br>
fi<br>
for mount in "${mounts[@]}"; do<br>
sudo umount --lazy "$mount" \<br>
|| {<br>
echo "ERROR: Failed to umount $mount."<br>
failed=true<br>
this_chroot_failed=true<br>
}<br>
done<br>
if ! $this_chroot_failed; then<br>
sudo rm -rf "$mock_root"<br>
fi<br>
done<br>
<br>
if $failed; then<br>
echo "Aborting."<br>
exit 1<br>
fi<br>
<br>
# remove mock system cache, we will setup proxies to do the caching and this<br>
# takes lots of space between runs<br>
shopt -u nullglob<br>
sudo rm -Rf /var/cache/mock/*<br>
<br>
# restore the permissions in the working dir, as sometimes it leaves files<br>
# owned by root and then the 'cleanup workspace' from jenkins job fails to<br>
# clean and breaks the jobs<br>
sudo chown -R "$USER" "$WORKSPACE"<br>
<br>
[ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson5198775129414653216.sh<br>
+ echo shell-scripts/mock_cleanup.sh<br>
shell-scripts/mock_cleanup.sh<br>
+ shopt -s nullglob<br>
+ WORKSPACE=<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/</a>><br>
+ cat<br>
_______________________________________________________________________<br>
#######################################################################<br>
# #<br>
# CLEANUP #<br>
# #<br>
#######################################################################<br>
+ logs=(./*log ./*/logs)<br>
+ [[ -n ./ovirt-system-tests/logs ]]<br>
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs<br>
./ovirt-system-tests/logs/<br>
./ovirt-system-tests/logs/<a href="http://mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/stdout_stderr.log./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/root.log./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/build.log./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/state.log./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/stdout_stderr.log./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/" rel="noreferrer" target="_blank">mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/stdout_stderr.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/root.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/build.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/state.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/stdout_stderr.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/</a><br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log<br>
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/stdout_stderr.log<br>
+ rm -rf ./ovirt-system-tests/logs<br>
+ failed=false<br>
+ mock_confs=("$WORKSPACE"/*/mocker*)<br>
+ for mock_conf_file in '"${mock_confs[@]}"'<br>
+ [[ -n <<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg</a>> ]]<br>
+ echo 'Cleaning up mock '<br>
Cleaning up mock<br>
+ mock_root=mocker-fedora-23-x86_64.fc23.cfg<br>
+ mock_root=mocker-fedora-23-x86_64.fc23<br>
+ my_mock=/usr/bin/mock<br>
+ my_mock+=' --configdir=<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests</a>'><br>
+ my_mock+=' --root=mocker-fedora-23-x86_64.fc23'<br>
+ my_mock+=' --resultdir=<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/</a>'><br>
+ echo 'Killing all mock orphan processes, if any.'<br>
Killing all mock orphan processes, if any.<br>
+ /usr/bin/mock --configdir=<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests</a>> --root=mocker-fedora-23-x86_64.fc23 --resultdir=<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/</a>> --orphanskill<br>
WARNING: Could not find required logging config file: <<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/logging.ini" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/logging.ini</a>.> Using default...<br>
INFO: mock.py version 1.2.17 starting (python version = 3.4.3)...<br>
Start: init plugins<br>
INFO: selinux enabled<br>
Finish: init plugins<br>
Start: run<br>
WARNING: Process ID 115551 still running in chroot. Killing...<br>
WARNING: Process ID 115576 still running in chroot. Killing...<br>
WARNING: Process ID 115577 still running in chroot. Killing...<br>
WARNING: Process ID 115578 still running in chroot. Killing...<br>
WARNING: Process ID 116634 still running in chroot. Killing...<br>
Finish: run<br>
++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg</a>><br>
+ mock_root=fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad<br>
+ [[ -n fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad ]]<br>
+ mounts=($(mount | awk '{print $3}' | grep "$mock_root"))<br>
++ mount<br>
++ awk '{print $3}'<br>
++ grep fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad<br>
+ [[ -n /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/proc ]]<br>
+ echo 'Found mounted dirs inside the chroot . Trying to umount.'<br>
Found mounted dirs inside the chroot . Trying to umount.<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/proc<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/sys<br>
sh: [115551: 1 (255)] tcsetattr: Inappropriate ioctl for device<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/dev/shm<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/dev/pts<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/var/cache/yum<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root<<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests</a>><br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/run/libvirt<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/var/lib/lago<br>
umount: /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/var/lib/lago: not mounted<br>
+ echo 'ERROR: Failed to umount /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/var/lib/lago.'<br>
ERROR: Failed to umount /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/var/lib/lago.<br>
+ failed=true<br>
+ for mount in '"${mounts[@]}"'<br>
+ sudo umount --lazy /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/proc/filesystems<br>
umount: /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/proc/filesystems: mountpoint not found<br>
+ echo 'ERROR: Failed to umount /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/proc/filesystems.'<br>
ERROR: Failed to umount /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644/root/proc/filesystems.<br>
+ failed=true<br>
+ for mock_root in '/var/lib/mock/*'<br>
+ this_chroot_failed=false<br>
+ mounts=($(mount | awk '{print $3}' | grep "$mock_root"))<br>
++ mount<br>
++ awk '{print $3}'<br>
++ grep /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644<br>
+ :<br>
+ [[ -n '' ]]<br>
+ false<br>
+ sudo rm -rf /var/lib/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad-91644<br>
+ true<br>
+ echo Aborting.<br>
Aborting.<br>
+ exit 1<br>
POST BUILD TASK : FAILURE<br>
END OF POST BUILD TASK : 1<br>
Recording test results<br>
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?<br>
Archiving artifacts<br>
_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org" target="_blank">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br>
<br>
</blockquote></div>
</div></div></div><div><br></div></div></div></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: <a href="tel:%2B972-9-7692018" value="+97297692018" target="_blank">+972-9-7692018</a><br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span style="color:rgb(0,0,0)"><span style="font-family:arial,helvetica,sans-serif"><span>
Best regards<br>
Tolik Litovsky<br>
RHEV-H Team<br>
Red Hat<br>
<br>
Red Hat: trustworthy, transformative technology. Powered by the community.<br>
Connect at <a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a></span></span></span></div></div></div></div></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: <a href="tel:%2B972-9-7692018" value="+97297692018" target="_blank">+972-9-7692018</a><br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>