<p dir="auto"><a href="http://kubekins.dls.corp.google.com:8081/job/kubernetes-pull-build-test-e2e-gce/45191/consoleFull" rel="nofollow">http://kubekins.dls.corp.google.com:8081/job/kubernetes-pull-build-test-e2e-gce/45191/consoleFull</a></p>
<p dir="auto">Unfortunately we don't have logs.</p>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/fejta/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/fejta">@fejta</a> <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/ixdy/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ixdy">@ixdy</a> - can you please take care of uploading logs in case of timeout?</p>
<p dir="auto">The kubernetes tarball is extracted inside the container in dockerized e2e, which gives us <code class="notranslate">kubernetes/cluster/log-dump.sh</code>. On timeout, we try to call <code class="notranslate">log-dump.sh</code>, but do so outside the container, so it's no longer available.</p>
<p dir="auto">We should probably move the timeout handling inside the dockerized e2e container.</p>