<div dir="ltr">I wrote that it was imageio because I have disabled deletion of /var/tmp on one job only (jenkins check-patch) and saw that on the same Jenkins slave only imageio check-patch and Jenkins check-patch run. Jenkins check-patch has nothing to do with libguestfs so I assumed that imageio did.<div>Here is a list of running jobs on the slave I have checked /var/tmp on. The imageio job cleans /var/tmp and jenkins job doesn't. </div><div><img src="cid:ii_15c3e86b398a4094" alt="Inline image 1" width="532" height="370"><br></div><div><br></div><div>Anyhow, I'll take your word on that and assume that the Jenkins build history has bugs and a VDSM or some other job run on that slave.</div><div><br></div><div>Now lets go back to the main interest of this thread. If we'll know, that whatever is being written to /var/tmp, can be considered as cache and can be used by the next run of the job that uses it, it might be a good idea not to clean /var/tmp. Jenkins is helping us with that by trying to run jobs on the same slave as much as possible.</div><div>We will start by monitoring our disks constantly to see how fast, if at all, they are getting full. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 24, 2017 at 6:28 PM, Michal Skrivanek <span dir="ltr"><<a href="mailto:mskrivan@redhat.com" target="_blank">mskrivan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div></div><div>To get back to the original point - I do not see a connection with imageio anywhere. It's libguestfs's temp dir. Now to decide what to do with it I think we should first understand which test uses/invokes libguestfs and for what purpose?</div><div><div class="h5"><div><br></div><div>On 24 May 2017, at 12:35, Gil Shinar <<a href="mailto:gshinar@redhat.com" target="_blank">gshinar@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, May 24, 2017 at 12:38 PM, Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, May 24, 2017 at 11:35 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 24 May 2017 at 11:17, Yaniv Kaul <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>> wrote:<br>
><br>
> /dev/shm is just as good. It's only 400MB.<br>
> Y.<br>
><br>
</span>Forgive my language but, hell no. This is not the gigantic Lago<br>
bare metals you are used to. We don't want GWT builds to start<br>
failing on running out of RAM.<br></blockquote><div><br></div></span><div>Buy more RAM.</div></div></div></div></blockquote><div><br></div><div>This is the best solution as having the cache on the ram will shorten the time of engine jobs. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="m_2698380505073442628HOEnZb"><font color="#888888"><div>Y.</div></font></span><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="m_2698380505073442628m_5861116491508076249HOEnZb"><div class="m_2698380505073442628m_5861116491508076249h5"><br>
--<br>
Barak Korren<br>
RHV DevOps team , RHCE, RHCi<br>
Red Hat EMEA<br>
<a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" rel="noreferrer" target="_blank">redhat.com/trusted</a><br>
</div></div></blockquote></span></div><br></div></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></blockquote></div><br></div></div>
</div></blockquote><blockquote type="cite"><div><span>______________________________<wbr>_________________</span><br><span>Devel mailing list</span><br><span><a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a></span><br><span><a href="http://lists.ovirt.org/mailman/listinfo/devel" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a></span></div></blockquote></div></div></div>
</blockquote></div><br></div>