<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35287#comment-35287 ]</pre>
<h3>Barak Korren commented on OVIRT-1702:</h3>
<p>{quote} I'm pretty sure in the past it was completely removed from the slave. {quote}</p>
<p>I'm pretty sure it was not, since code handling this has not been significantly changed since David first wrote it.</p>
<p>The workspace including the source checkout does get completely remove when a <strong>different job</strong> starts running on the node. But as long as its the same job, the workspace stays as-is.</p>
<p>{quote}</p>
<pre>Is there any good reason for not cleaning the slave after job completion?</pre>
<p>{quote}</p>
<p>Yes. Re-cloning the whole git repo every time we run something will significantly slow things down.</p>
<p>Also we do not clean the slave up <strong>after</strong> the execution, we clean it <strong>before the next one</strong>. This has the benefit of allowing us to debug failed runs and also prevent the next run from failing if the post-run code was not reached for some reason. But a side-affect of this is that the more cleanup steps we have the longer the latency our users experience between submitting patchs and having their check-patch code run, so we try to keep it to a minimum.</p>
<blockquote><h3>Jenkins STD-CI are running in dirty mock chroots</h3>
<pre> Key: OVIRT-1702
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1702
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra</pre>
<p>Example: <a href="http://jenkins.ovirt.org/job/ovirt-wgt_master_check-patch-fc26-x86_64/11/console">http://jenkins.ovirt.org/job/ovirt-wgt_master_check-patch-fc26-x86_64/11/console</a> <strong>09:44:06</strong> + ./automation/build-artifacts.sh*09:44:06* + [[ -d exported-artifacts ]]*09:44:06* + mkdir -p exported-artifacts*09:44:06* + [[ -d tmp.repos/SOURCES ]]*09:44:06* + mkdir -p tmp.repos/SOURCES*09:44:06* + git clone git://anongit.freedesktop.org/spice/spice-nsis*09:44:06* fatal: destination path ‘spice-nsis’ already exists and is not an empty directory. jobs should run in clean chroots. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>> <<a href="http://www.teraplan.it/redhat-osd-2017/">http://www.teraplan.it/redhat-osd-2017/</a>></p></blockquote>
<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-2BCmpYLyzYS3r1Q939T2sgz3-2BE94PKA29y1dvYVsE9-2BcfuSKNyiE7ttT-2Bju2NuI5lhOy5l3WV5Tj7DGNa-2FHUHBd5A2LCSRHkQ5evKJDW9sDV8wy00mXJMvj80ufIri2ypMH59WhWd4H6QRVnjkgh5mLtI-2FTGk-2BgSTZSHPFN29J82OBNL63P7GpWzaqZeIN-2Blnbw-3D-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>