From b80e93495b53d895cf028a352c537193f0ff52c6 Mon Sep 17 00:00:00 2001 From: mintaka Date: Thu, 15 Oct 2026 02:43:03 -0400 Subject: [PATCH] ci(compass): give the pgtest suite a 25m go test bound (RIG-5325) internal/store's test binary now runs 11-15m on shared runners (665s on main, 900s+ on #2285 and #2290), so the 15m -timeout killed passing runs. Raise it to 25m and the job to 40m. Sharding stays a deferred design question. Co-authored-by: Matt Wilkinson --- .github/workflows/ci.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index c93688c0e..7a4981c96 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -656,7 +656,8 @@ jobs: needs.setup.outputs.pgtest_affected == 'true') # Passing runs take 18-19.5m (the -race suite alone is ~17m); at 20, a run # whose packages had all passed was cancelled during the sqlc-vet bootstrap. - timeout-minutes: 30 + # 40 leaves room for the 25m go test bound below plus the bootstrap. + timeout-minutes: 40 env: # The Real-Postgres suites bind AF_UNIX sockets under t.TempDir(); the # runner's default TMPDIR overflows sun_path's 108-byte cap. Same reason as @@ -804,9 +805,10 @@ jobs: # which would otherwise abort before the log is ever printed. The # explicit -timeout exceeds the job's slowest suite: on the default 10m a # wedged test panics mid-run and the panic, not the failure, is the story. + # internal/store alone runs 11-15m on shared runners, so 15m was too tight. run: | rc=0 - go test -tags pgtest -race -v -timeout 15m ./... >/tmp/pgtest.log 2>&1 || rc=$? + go test -tags pgtest -race -v -timeout 25m ./... >/tmp/pgtest.log 2>&1 || rc=$? cat /tmp/pgtest.log exit "$rc"