From 88f300d74d93bfee6750100ee5d3056672cad3ad Mon Sep 17 00:00:00 2001 From: Michael Bolin Date: Sat, 25 Apr 2026 10:03:01 -0700 Subject: [PATCH] fix: increase Bazel timeout to 45 minutes (#19578) Unfortunately, if most of the build graph is invalidated such that there are few cache hits, the Windows Bazel build for all the tests often takes more than `30` minutes, so this PR increases the timeout to `45` minutes until we set up distributed builds. --- .github/workflows/bazel.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/bazel.yml b/.github/workflows/bazel.yml index fa1ce7277..bfb10ab6a 100644 --- a/.github/workflows/bazel.yml +++ b/.github/workflows/bazel.yml @@ -17,7 +17,11 @@ concurrency: cancel-in-progress: ${{ github.ref_name != 'main' }} jobs: test: - timeout-minutes: 30 + # Ideally, this would be only 30 minutes, but a no-cache-hit Windows build + # seems to trip this limit and starting over is painful when it happens. + # Ultimately we need true distributed builds (e.g., + # https://www.buildbuddy.io/docs/rbe-setup/) to speed things up. + timeout-minutes: 45 strategy: fail-fast: false matrix: