Skip to content

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

Merged
mattwilkinsonn merged 1 commit into
mainfrom
ci/rig-5325-pgtest-timeout
Oct 15, 2026
Merged

mattwilkinsonn merged 1 commit into
mainfrom
ci/rig-5325-pgtest-timeout

Conversation

@rigel-mintaka

@rigel-mintaka rigel-mintaka commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Summary

pgtest's internal/store test binary hit the 15m go test -timeout on #2285 and #2290 (900s). The same package took 665s on main and 733s one run earlier, and no test hung (timings on RIG-5325). Shared-runner variance now spans the whole margin.

  • go test -timeout 15m → 25m.
  • Job timeout-minutes 30 → 40, so the job bound still sits above the go test bound plus the bootstrap steps.

Sharding internal/store is the deferred pgtest-sharding question in the compass CI PR-speed design record. This PR does not shard it.

Verification

  • actionlint: same 17 findings as main, no new ones.
  • The next pgtest run on this PR exercises the new bound.

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 <matt@rigel.build>
@trunk-io

trunk-io Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

😎 This pull request was merged.

@linear-code

linear-code Bot commented Oct 15, 2026

Copy link
Copy Markdown

RIG-5325

@github-actions

Copy link
Copy Markdown

Compass engineering docs preview: https://ci-rig-5325-pgtest-timeout.compass-eng-docs.pages.dev

Deployed from ci/rig-5325-pgtest-timeout at b80e934.

@rigel-mintaka
rigel-mintaka marked this pull request as ready for review October 15, 2026 07:24
@mattwilkinsonn
mattwilkinsonn merged commit 08ec3c5 into main Oct 15, 2026
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants