ci: job timeout and --blame-hang so a stalled test step fails located, not after 3h of silence (lmxopcua#718)

Run 959 (job 3552) was silent from 13:39 for 3h12m and was failed by the server reaper with no cause. Pre-#707 runs 935/938/941/942/947/959 all ended at 189-193 min; no run since 76bdca90 exceeds 82 min (healthy ~53). Adds timeout-minutes 120 and blame-hang (20m, no dump) to the whole-solution test step. Claude-Session: https://claude.ai/code/session_01GT67AEHd2Acv1YPwGfXEoV
2026-11-09 16:22:40 -05:00
parent 380ec541c2
commit c9288a56c0
2 changed files with 14 additions and 0 deletions
@@ -18,6 +18,11 @@ one run is active; an active run is not cancelled, but a newer pending run may
 supersede an older pending run. The group does not serialize other repositories
 using the same host.

+Stall guards (#718): the job has `timeout-minutes: 120` (healthy runs take about 60 minutes)
+and the test step passes `--blame-hang --blame-hang-timeout 20m --blame-hang-dump-type none`, so a
+test that stops making progress is killed and named in the log instead of leaving hours of silence
+(run 959 stalled 3h12m until the server reaper failed it).
+
 To reproduce the bounded test leg after restore and Release build:

 ```bash