Skip to content

Commit c660d95

Browse files
cdeustclaude
andcommitted
ci: bound the test job with timeout-minutes
The `test` job inherited GitHub's 360-minute default, so a hung leg (release run 30741657854: FlashRank's timeout-less `requests.get`, CHANGELOG 4.17.1) could hold the whole workflow for hours. Measured 2026-09-03 over the last 12 green `main` runs: Test (Python 3.12) took 15-22 min, the other three legs 7-10 min. 45 minutes is about twice the measured maximum. Co-Authored-By: Claude Fable 5.1 <[email protected]>
1 parent c5ec018 commit c660d95

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

‎.github/workflows/ci.yml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,17 @@ jobs:
2828
test:
2929
name: Test (Python ${{ matrix.python-version }})
3030
runs-on: ubuntu-latest
31+
# Bound a hung leg instead of inheriting GitHub's 360-minute default:
32+
# release run 30741657854 (v4.17.0, CHANGELOG 4.17.1) sat in FlashRank's
33+
# timeout-less `requests.get` until pytest-timeout fired, and only that
34+
# per-test guard, not the job, ever bounded the suite.
35+
# source: measured 2026-09-03 over the last 12 green `main` runs of this
36+
# workflow (gh run list --status success): the slowest leg, Test (Python
37+
# 3.12, the only one running the extended checks), took 15-22 min
38+
# (max 22 min at e8ae24c8); the other three legs took 7-10 min. 45 min is
39+
# about twice that measured maximum, so a slow runner still passes while a
40+
# stalled job is cut within one ordinary run's wall time.
41+
timeout-minutes: 45
3142
strategy:
3243
fail-fast: false
3344
matrix:

0 commit comments

Comments
 (0)