Skip to content

Commit ece0c2d

Browse files
committed
ci(lint): raise the lint job timeout from 30 to 45 minutes
The lint job's single-process cppcheck pass now takes 22-29 minutes: the src tree grew about 60 % in files in ten days (210 files / 7.4 MB on 2026-10-04, 335 / 11.2 MB since 2026-10-12) while the cppcheck flags stayed the same. Three runs on 2026-10-13 (38330125249, 38345850562, 38370789949) were cancelled at the 30-minute cap with cppcheck still running and every earlier lint step clean. A cancelled lint is a hard stop for the release graph, and the dry run's tests need lint to pass. 45 minutes puts the bound back where only a genuine hang reaches it. Parallel cppcheck (-j) would be faster, but it changes cppcheck's whole-program checks; it is left for its own change with a findings-equivalence proof. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
1 parent 8aa5259 commit ece0c2d

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

‎.github/workflows/_lint.yml‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,11 @@ jobs:
2323
runs-on: ubuntu-24.04
2424
# 15 min proved too tight on a slow runner day and a timed-out lint reads
2525
# as "cancelled", which the release graph must treat as a hard stop; keep
26-
# a bound, but one only a genuine hang can hit (normal runtime ~5 min).
27-
timeout-minutes: 30
26+
# a bound, but one only a genuine hang can hit. 30 min stopped being that
27+
# in 2026-10: single-process cppcheck over a src tree that grew ~60 % in
28+
# files took the lint step from ~8 to 22-29 min, and three runs on
29+
# 2026-10-13 were cancelled at 30 min with cppcheck still alive.
30+
timeout-minutes: 45
2831
steps:
2932
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
3033

0 commit comments

Comments
 (0)