ci: raise test timeout 20m → 30m; update comments (mc#1099)

2026-05-15 10:02:27 +00:00
parent 31f718b04e
commit 08e148ceb1
1 changed files with 12 additions and 12 deletions
@@ -145,11 +145,11 @@ jobs:
    # the diagnostic step with its own continue-on-error: true (line 203).
    # Flip confirmed by CI / Platform (Go) status = success on main HEAD 363905d3.
    continue-on-error: false
-    # Job-level ceiling. The go test step below runs with a per-step 20m timeout;
-    # this cap catches any step that leaks past that. Set well above 20m so
-    # the per-step timeout is the active constraint. Raised from 15m to 50m
-    # to account for golangci-lint taking ~10m on cold runners (--no-config)
-    # plus ~12m for test suite on cold runner (mc#1099).
+    # Job-level ceiling. The go test step below runs with a per-step 30m timeout;
+    # this cap catches any step that leaks past that. Set well above 30m so
+    # the per-step timeout is the active constraint. Raised to 50m
+    # to account for golangci-lint ~10m on cold runner (--no-config) plus
+    # test suite ~19m on cold runner (mc#1099).
    timeout-minutes: 50
    defaults:
      run:
@@ -198,13 +198,13 @@ jobs:
      - if: always()
        name: Run tests with race detection and coverage
        # Explicit timeout: cold runner cache causes OOM kills at ~4m39s on the
-        # full ./... suite with race detection + coverage. A 20m per-step timeout
-        # lets the suite complete on cold cache (~5-12m) while failing cleanly
-        # instead of OOM-killing. The job-level timeout (50m) is a backstop.
-        # mc#1099: raised from 10m → 15m → 20m. Cold runner: golangci-lint ~10m
-        # + test suite ~8-12m = up to 22m total. 15m was still too tight (PR #1151
-        # Platform (Go) failed at 18m on a very-cold runner). 20m gives headroom.
-        run: go test -race -timeout 20m -coverprofile=coverage.out ./...
+        # full ./... suite with race detection + coverage. A 30m per-step timeout
+        # lets the suite complete on cold cache (~19m observed) while failing
+        # cleanly instead of OOM-killing. The job-level timeout (50m) is a
+        # backstop. mc#1099: raised 10m → 15m → 20m → 30m. Cold runner:
+        # golangci-lint ~10m + test suite ~19m = ~29m total. 20m was too tight
+        # (PR #1151 failed at 19m5s with golangci-lint ~10m + test ~19m).
+        run: go test -race -timeout 30m -coverprofile=coverage.out ./...

      - if: always()
        name: Per-file coverage report