From 6181943e3229ebf6439bfcd3a8a91ff5020ec4f5 Mon Sep 17 00:00:00 2001 From: Joe Rickerby Date: Tue, 13 Sep 2022 23:58:09 +0300 Subject: [PATCH] Increase Cirrus CI timeout (#1267) Gives us a little more flex for the Cirrus build. I've set these to the maximum because we already use pytest-timeout to catch stalled tests, so there's little need to be conservative. MacOS ARM and aarch64 linux are currently running at 5 and 20 minutes respectively, so no need to increase their limits. See https://github.com/pypa/cibuildwheel/runs/8321188914 for an example timeout on Linux x86 --- .cirrus.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.cirrus.yml b/.cirrus.yml index 7385d88a..e85ef479 100644 --- a/.cirrus.yml +++ b/.cirrus.yml @@ -6,6 +6,7 @@ run_tests: &RUN_TESTS linux_x86_task: + timeout_in: 120m compute_engine_instance: image_project: cirrus-images image: family/docker-builder @@ -33,7 +34,7 @@ linux_aarch64_task: windows_x86_task: # The task takes ~55 minutes while the timeout happens # after 60 minutes by default, let's allow some wiggle room. - timeout_in: 90m + timeout_in: 120m windows_container: image: cirrusci/windowsservercore:visualstudio2022 cpu: 8