From fdac01d93a993a71d1e738a1b65de2585010212d Mon Sep 17 00:00:00 2001 From: yhirose Date: Tue, 28 Apr 2026 08:37:07 +0900 Subject: [PATCH] Cap issue-2431 repro job at 5 minutes The bug manifests as orphan getaddrinfo_a resolver workers that keep the runner from completing job teardown -- the previous run had all steps succeed in ~1m37s but then hung in "Cleaning up orphan processes" for ~57m before GitHub force-killed the job. A job-level timeout-minutes makes the failure signal fast and predictable: bug present -> killed at 5 min, bug fixed -> ~2 min pass. Step-level timeout isn't enough since the hang is in post-job cleanup, not the test step. --- .github/workflows/test.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml index 9e57c07..2859b70 100644 --- a/.github/workflows/test.yaml +++ b/.github/workflows/test.yaml @@ -129,6 +129,11 @@ jobs: github.event.pull_request.head.repo.full_name != github.event.pull_request.base.repo.full_name) || (github.event_name == 'workflow_dispatch' && github.event.inputs.test_linux == 'true') name: issue-2431 repro (Linux + ASAN) + # The bug manifests as orphan getaddrinfo_a resolver workers that prevent + # the runner from completing job teardown ("Cleaning up orphan processes" + # hangs for ~1h until forced shutdown). Cap the whole job at 5 min so the + # failure surfaces fast: bug present -> killed at 5min, bug fixed -> ~2min. + timeout-minutes: 5 steps: - name: checkout uses: actions/checkout@v4