[ https://ovirt-jira.atlassian.net/browse/OVIRT-1702?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1702: ------------------------------------- {quote} I'm pretty sure in the past it was completely removed from the slave. {quote} I'm pretty sure it was not, since code handling this has not been significantly changed since David first wrote it. The workspace including the source checkout does get completely remove when a *different job* starts running on the node. But as long as its the same job, the workspace stays as-is. {quote} Is there any good reason for not cleaning the slave after job completion? {quote} Yes. Re-cloning the whole git repo every time we run something will significantly slow things down. Also we do not clean the slave up *after* the execution, we clean it *before the next one*. 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. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)