From 730af3239d2287b0add73e0f9119871320f60377 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=F0=9F=87=BA=F0=9F=87=A6=20Sviatoslav=20Sydorenko=20=28?= =?UTF-8?q?=D0=A1=D0=B2=D1=8F=D1=82=D0=BE=D1=81=D0=BB=D0=B0=D0=B2=20=D0=A1?= =?UTF-8?q?=D0=B8=D0=B4=D0=BE=D1=80=D0=B5=D0=BD=D0=BA=D0=BE=29?= Date: Thu, 30 Oct 2025 16:48:46 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=A7=AA=20Set=20timeouts=20for=20CI=20jobs?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sometimes, AZP would mark steps in jobs as cancelled when they've actually exited successfully but on the boundary of the default 60-minute timeout. Such logs might be difficult to reason about. Additionally, `entry-point.sh` sets a 60-minute timeout for the main test invocation but it would never trigger earlier that AZP would kill such a job as the job-global timeout was 60 minutes already and it'd always be hit earlier than the test runner one. The patch sets maximum observable job timeouts with extra buffer to account for flakiness. PR #86073 Co-authored-by: Matt Clay --- .azure-pipelines/templates/coverage.yml | 1 + .azure-pipelines/templates/test.yml | 1 + 2 files changed, 2 insertions(+) diff --git a/.azure-pipelines/templates/coverage.yml b/.azure-pipelines/templates/coverage.yml index b518df280c2..2d5614fccab 100644 --- a/.azure-pipelines/templates/coverage.yml +++ b/.azure-pipelines/templates/coverage.yml @@ -7,6 +7,7 @@ jobs: - job: Coverage displayName: Code Coverage container: $[ variables.defaultContainer ] + timeoutInMinutes: 10 workspace: clean: all steps: diff --git a/.azure-pipelines/templates/test.yml b/.azure-pipelines/templates/test.yml index 3df72632a8c..8fc2fb269ee 100644 --- a/.azure-pipelines/templates/test.yml +++ b/.azure-pipelines/templates/test.yml @@ -12,6 +12,7 @@ jobs: - job: test_${{ replace(replace(replace(replace(job.test, '/', '_'), '.', '_'), '-', '_'), '@', '_') }} displayName: ${{ job.name }} container: $[ variables.defaultContainer ] + timeoutInMinutes: 65 workspace: clean: all steps: