Skip to content

Cap CI test jobs at 30 minutes - #5869

Merged
ramonsmits merged 1 commit into
masterfrom
ramon/ci-job-timeout
Sep 9, 2026
Merged

ramonsmits merged 1 commit into
masterfrom
ramon/ci-job-timeout

Conversation

@ramonsmits

Copy link
Copy Markdown
Member

The build job had no timeout-minutes, so a job whose runner was lost or whose test host hung on infrastructure kept the runner for the 6 hour default until the next push cancelled the run (e.g. the 46 min Windows-IBMMQ and 52 min Windows-SqlServer jobs on recent runs).

Across the last 60 CI runs no healthy job took longer than 18 minutes (Windows-SqlServer, 17.6 min worst case), so 30 leaves comfortable headroom while ending dead jobs promptly.

The build job had no timeout, so a job whose runner was lost or whose test
host hung on infrastructure kept the runner for the 6 hour default until the
next push cancelled the run. Across the last 60 runs no healthy job took
longer than 18 minutes.
@ramonsmits
ramonsmits merged commit 227dc4b into master Sep 9, 2026
36 checks passed
@ramonsmits
ramonsmits deleted the ramon/ci-job-timeout branch September 9, 2026 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants