Timeout CI build job after 30 minutes #1033
Conversation
|
Looks good. The only thing I don't know is what happens if one of the matrix jobs has to wait for a free hosted runner before it can start - does the 30 minutes apply from the start of each matrix job or is across all matrix jobs and thus ones that started late could get timed out earlier than 30 minutes? I read the docs but didn't find the answer to this. I wondered because if you say sane jobs finish in 10 minutes then maybe 30 minutes is a bit on the high side and could be lower. |
|
Failing test is caused by linux.del.com being down, which seems usual: https://www.dell.com/community/Systems-Management-General/linux-dell-com-down-or-decomissioned/td-p/7731548 I've opened #1034 |
#1034 is closed. I need to rebase this PR to master and see if tests now pass. |
lbolla
force-pushed
the
issue-1032-ci-timeouts
branch
from
15c2ac2
to
a840fb9
Compare
Fix #1032
Fixes #
Description of the Change
Add a 30 minutes timeout to CI build test, to avoid runaway tests.
Currently sane unittests run in less than 10 minutes.