From 1dd45d6016a56f8c3e36b2acb2b0d734b8ebce5d Mon Sep 17 00:00:00 2001 From: Aiden Grossman Date: Sat, 18 Oct 2025 00:48:03 +0000 Subject: [PATCH] [Github] Add Timeouts to Premerge Jobs The premerge jobs currently use the default timeouts. If something ends up hanging, they run for the full six hours. Given our jobs never actually take six hours other than when something hangs, we should set the timeouts lower to not use up machine capacity when something does go wrong. These limits were currently chosen conservatively, being a decent amount above the maximum run times I have seen over the past couple months, excluding six hour timeouts. --- .github/workflows/premerge.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/premerge.yaml b/.github/workflows/premerge.yaml index 03c0c01d382ff..951fc16bed215 100644 --- a/.github/workflows/premerge.yaml +++ b/.github/workflows/premerge.yaml @@ -62,6 +62,7 @@ jobs: with: fetch-depth: 2 - name: Build and Test + timeout-minutes: 120 continue-on-error: ${{ runner.arch == 'ARM64' }} run: | git config --global --add safe.directory '*' @@ -149,6 +150,7 @@ jobs: echo "windows-runtimes=${runtimes_to_build}" >> $GITHUB_OUTPUT echo "windows-runtimes-check-targets=${runtimes_check_targets}" >> $GITHUB_OUTPUT - name: Build and Test + timeout-minutes: 180 if: ${{ steps.vars.outputs.windows-projects != '' }} shell: cmd run: |