From d2c2fa775075bd331e919a9136487b9cd99f5106 Mon Sep 17 00:00:00 2001 From: Matthias Bertschy Date: Thu, 10 Sep 2026 07:57:01 +0200 Subject: [PATCH] ci: cap component-tests jobs at 30 minutes A stuck post-step (e.g. actions/setup-go's cache-save) can otherwise run for the full 6-hour hosted-runner ceiling, and GitHub never flushes a force-cancelled job's log tail -- turning an unrelated infra stall into an undiagnosable multi-hour mystery. go test's own --timeout=20m already bounds real test hangs; this just bounds everything else around it too. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01LCMGT6Po2tSr1VEDVrbbYd --- .github/workflows/component-tests.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/component-tests.yaml b/.github/workflows/component-tests.yaml index b46c57153..bc252d1b7 100644 --- a/.github/workflows/component-tests.yaml +++ b/.github/workflows/component-tests.yaml @@ -70,6 +70,7 @@ jobs: runs-on: ubuntu-latest needs: build-and-push-image continue-on-error: true + timeout-minutes: 30 strategy: matrix: test: [