ci: cap every CI job with timeout-minutes - #415
Merged
Conversation
Lint hung for 6 hours on PR 411 (apt-get stalling against a flaky mirror) until GitHub's default 360-minute job timeout finally killed it, and because test-e2e needs lint, it sat SKIPPED the whole time too. No job here previously set an explicit cap, so any future hang anywhere blocks a PR for hours before anyone notices instead of failing fast. Caps are generous relative to observed run times (Build ~2m, Unit Tests ~1.5m, Unit Tests (root) ~1m, Lint ~3m, E2E ~5m): 15 minutes for lint/build/unit jobs, 25 for e2e. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ecv
approved these changes
Aug 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR #411's
Lintjob hung 6 hours onapt-get install clang-18 llvm-18 linux-libc-dev, stuck against a flaky mirror.GitHub's default 360-minute job timeout eventually cancelled it.
test-e2eneedslint, so it satSKIPPEDthe whole time.No job in
ci.yamlsetstimeout-minutes. Any hang, anywhere, blocks a PR for hours with no signal something is wrong.This adds
timeout-minutesto every job, sized against observed run times (Build ~2m, Unit Tests ~1.5m, Unit Tests (root) ~1m, Lint ~3m, E2E ~5m):lint,test-unit,test-unit-root,build: 15 minutestest-e2e: 25 minutesTest plan
Lintjob on PR fix: Restore IPv6-only Cilium networking in containerlab labs #411. It completed in ~3 minutes, well inside the new cap.