<div dir="auto"><div>The jenkins level timeout dates back to the days on the looong looong upgrade test jobs.<div dir="auto"><br></div><div dir="auto">Then as today it was designed as last resort failsfae, and typically leaves a mess around.</div><div dir="auto"><br></div><div dir="auto">You are still seeing stuff running after it because it is not supposed to kill the clenup scripts or we're guaranteed to get dirty slaves.</div><div dir="auto"><br></div><div dir="auto">We do need to figure out what caused the simple docker restart to not finish for 6 hours. I suspect were seeing symptoms and confusing log buffer behaviour and not the real issue.</div><div dir="auto"><br><br><div data-smartmail="gmail_signature" dir="auto">Barak Korren<br><a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>RHCE, RHCi, RHV-DevOps Team<br><a href="https://ifireball.wordpress.com/">https://ifireball.wordpress.com/</a></div></div><br><div class="gmail_extra"><br><div class="gmail_quote">בתאריך 30 במאי 2017 07:52 PM, "Nir Soffer" <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>> כתב:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">See <a href="http://jenkins.ovirt.org/job/ovirt-release_4.1_build-artifacts-el7-x86_64/205/console" target="_blank">http://jenkins.ovirt.org/<wbr>job/ovirt-release_4.1_build-<wbr>artifacts-el7-x86_64/205/<wbr>console</a><div><br></div><div>Build stuck after 16 minutes (using elapsed time):</div><div><pre style="box-sizing:border-box;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51);font-size:16px"><span class="m_2609358087050730719inbox-inbox-timestamp" style="box-sizing:border-box"><b style="box-sizing:border-box">00:16:49.203</b> </span>+ sudo systemctl restart docker</pre><pre style="box-sizing:border-box;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51);font-size:16px"><br></pre><pre style="box-sizing:border-box;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51);font-size:16px">Failure detected after 6 hours:
<span class="m_2609358087050730719inbox-inbox-timestamp" style="box-sizing:border-box"><b style="box-sizing:border-box">06:00:07.301</b> </span>Build timed out (after 360 minutes). Marking the build as failed.
</pre></div><div><br></div><div>But the job is still running:</div><div><pre id="m_2609358087050730719inbox-inbox-out" class="m_2609358087050730719inbox-inbox-console-output" style="box-sizing:border-box;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51);font-size:16px"><pre style="box-sizing:border-box;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px"><span class="m_2609358087050730719inbox-inbox-timestamp" style="box-sizing:border-box"><b style="box-sizing:border-box">06:00:08.490</b> </span>+ xargs -r sudo docker rm -f
</pre></pre><br class="m_2609358087050730719inbox-inbox-Apple-interchange-newline"></div><div>Why build-artifacts job needs 6 hours timeout?</div><font color="#888888"><div><br></div><div>Nir</div></font></div>
<br>______________________________<wbr>_________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/infra</a><br>
<br></blockquote></div><br></div></div></div>