ci: bound every workflow job with timeout-minutes

mirror of https://github.com/yeasy/docker_practice.git synced 2026-08-10 16:37:34 +00:00

A wedged Chrome/mdPress step held a harness runner for 27 minutes yesterday
(normal run: ~4 min) and ignored `gh run cancel`; it only stopped because that
job happened to carry timeout-minutes: 30. An audit found 66 of the 101 jobs
across the cluster had no timeout at all — the same hang there would have held
a runner for GitHub's 6-hour default.

Values come from measured run history, not guesses. Across ~120 successful
runs the slowest workflow tops out at 10 min (Update Preview Publications),
CI at 6.5, Update Preview PDF at 4.8:

  30 min — jobs that run Chrome/mdPress/pandoc (3x the observed max, and the
           value harness already used)
  15 min — release, publish, deploy, check-link, chaincode-tests
  10 min — dependabot auto-merge

Every value has at least 6x headroom over its job's observed maximum, so this
should never turn a slow-but-working run into a failure.

Verified: all 72 workflow files still parse, and all 101 jobs now carry an
integer timeout in range.

This commit is contained in:

yeasy

2026-07-23 08:26:48 -07:00

parent 7c96d19fd4

commit 52f6c73478

6 changed files with 9 additions and 0 deletions

									
										.github/workflows/check-link.yml
									
		+1
		
												View File
												
				@@ -9,6 +9,7 @@ permissions:

				jobs:

				  check-link:

				    runs-on: ubuntu-latest

				    timeout-minutes: 15

				    steps:

				      - name: Checkout

				        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1