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.
This commit is contained in:
yhirose
2026-04-28 08:37:07 +09:00
parent 6fd2f93b5c
commit fdac01d93a

View File

@@ -129,6 +129,11 @@ jobs:
github.event.pull_request.head.repo.full_name != github.event.pull_request.base.repo.full_name) || 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') (github.event_name == 'workflow_dispatch' && github.event.inputs.test_linux == 'true')
name: issue-2431 repro (Linux + ASAN) 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: steps:
- name: checkout - name: checkout
uses: actions/checkout@v4 uses: actions/checkout@v4