tag:help.appveyor.com,2012-11-13:/discussions/problems/26295-hosted-runners-job-killed-after-60-mins-despite-longer-timeoutAppVeyor: Discussion 2020-03-10T20:36:06Ztag:help.appveyor.com,2012-11-13:Comment/480913152020-02-16T03:02:26Z2020-02-16T03:02:26ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>Hi Jan,</p>
<p>That build you gave a link to failed in 10 seconds, not cancelled by timeout. Is that the correct build URL?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/480913152020-02-16T03:05:31Z2020-02-16T03:05:31ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>Hi,</p>
<p>sorry, you're right I've updated the link. The first link was meant for <a href="https://help.appveyor.com/discussions/problems/26293-quote-branch-name-during-checkout">https://help.appveyor.com/discussions/problems/26293-quote-branch-n...</a></p>
<p>Jan</p></div>Jan Veselytag:help.appveyor.com,2012-11-13:Comment/480913152020-02-16T03:41:01Z2020-02-16T03:41:01ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>Right, running on a self-hosted agent doesn't automatically increase timeout.<br>
However, you can configure project-specific build timeout on "General" tab of project settings.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/480913152020-02-16T03:44:36Z2020-02-16T03:45:16ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>I did, that's the problem. The project timeout is set to 80 minutes and it reports as 'timed out' in 1h 20 mins, which is correct.</p>
<p>The problem is that it did nothing in the last 20 mins.<br>
The container stopped after 60mins. I checked 'docker ps', as well as the last line of output (which is at 1:00:57).</p>
<p>Is there another timeout setting on the runner side that needs to be bumped above 60 mins?</p></div>Jan Veselytag:help.appveyor.com,2012-11-13:Comment/480913152020-02-16T03:47:27Z2020-02-16T03:47:27ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>I see. When you run the build in the container could you open http://localhost:5020 on Docker machine and check if what time should the build finish?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/480913152020-02-16T03:59:48Z2020-02-16T04:00:10ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>I've only remote access to the machine. Is there a resource I can GET using <code>nc</code> to retrieve the info?<br>
I found these lines in the log:<br></p>
<pre>
<code>Feb 15 14:37:44 baltix appveyor-host-agent[2214]: info: Appveyor.HostAgent.Docker.WorkerCloud[0]
Feb 15 14:37:44 baltix appveyor-host-agent[2214]: [worker-557-004] Received job message: JobId=2vqf4opd9jhvc980, JobName=jvesely/llvm-project-llvm/36, JobTimeout=60, ImageName=Ubuntu</code>
</pre></div>Jan Veselytag:help.appveyor.com,2012-11-13:Comment/480913152020-02-16T15:32:03Z2020-02-16T15:32:03ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>Looks like there is a bug. We are going to fix it and deploy update. I've created an issue: <a href="https://github.com/appveyor/ci/issues/3317">https://github.com/appveyor/ci/issues/3317</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/480913152020-03-09T23:42:34Z2020-03-09T23:42:34ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>Hi Jan,</p>
<p>Timeout for BYOC clouds have been fixed. Let me know how that worked.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/480913152020-03-10T20:31:32Z2020-03-10T20:31:32ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>Hi,</p>
<p>I can see the logs now currently report >=60 min timeouts and jobs completing after >60 mins. I think it's fixed.<br>
Thank you!</p></div>Jan Veselytag:help.appveyor.com,2012-11-13:Comment/480913152020-03-10T20:34:46Z2020-03-10T20:34:46ZHosted runners: Job killed after 60 mins despite longer timeout<div><p>Cool, thanks for the update!</p></div>Feodor Fitsner