From 8e1c73e77211a560ca973c49f89c641345d7a9b8 Mon Sep 17 00:00:00 2001
From: Remylus Losius <remyluslosius@gonaibo.com>
Date: Fri, 17 Jul 2026 17:28:12 -0400
Subject: [PATCH] ci: raise go test -race timeout 600s -> 900s
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The internal/server suite (~470s without -race) rides near the old per-package
600s limit under `go test -race -p 4`, so it intermittently times out on slower
/ more-contended runners — e.g. Go CI #976 on main (post-#748 merge) timed out
at 10m0s while the identical commit passed on the PR branch. Recent test
additions pushed it over the edge. Raise the per-package timeout to 900s for
headroom; a genuine hang still fails within 15 min.
---
 .github/workflows/go-ci.yml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/go-ci.yml b/.github/workflows/go-ci.yml
index 3e1b85ee..d29deed5 100644
--- a/.github/workflows/go-ci.yml
+++ b/.github/workflows/go-ci.yml
@@ -258,7 +258,11 @@ jobs:
           # ships inside the kensa module, so api-system-scan-config/AC-08 runs
           # here instead of skipping (100% outcome coverage requires it).
           export OPENWATCH_KENSA_RULES_DIR="$(go list -m -f '{{.Dir}}' github.com/Hanalyx/kensa)/rules"
-          go test -race -json -timeout 600s -p 4 ./... > /tmp/go-test.json
+          # -timeout is per package. internal/server is the heavy suite (~470s
+          # without -race) and rides near the old 600s limit under -race + -p 4
+          # DB contention, so it intermittently times out (e.g. main run #976).
+          # 900s gives headroom without masking a genuine hang.
+          go test -race -json -timeout 900s -p 4 ./... > /tmp/go-test.json
           EXIT=$?
           if [ "$EXIT" -ne 0 ]; then
             echo "::group::Failed tests"