Skip to content

ci(compass): give the pgtest suite a 25m go test bound (RIG-5325) #2301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mattwilkinsonn merged 1 commit into from
Oct 15, 2026
Merged

ci(compass): give the pgtest suite a 25m go test bound (RIG-5325) #2301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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"

Expand Down
Loading