ci: peel pgtest into its own peer job (RIG-2696) - #607
Merged
Conversation
Move the real-Postgres suites out of the monolithic `gates` job into a dedicated `pgtest` peer job behind the single `CI` rollup, so a Postgres-service flake or the slow `-race` suite no longer serializes behind the whole moon battery — the two lanes now fail independently and a service-container flake reds only `pgtest`, not the hermetic gate. The postgres service block and both Real-Postgres steps (the suite and its assert-ran guard) move verbatim; the checkout + install-nix + phase-one toolchain bootstrap is reproduced (go on PATH is all pgtest needs). The `gates` job loses its service and two steps and is renamed `Gates (moon)`; nothing else in it changes. The `CI` rollup gains `pgtest` in `needs` and a third result assertion, so the single required check is unchanged. pgtest runs unconditionally on every gate event at this step; a later task gates it on the Go affected-closure so an unaffected PR pays zero. First task (T1) of the CI job-decomposition plan frozen in docs/designs/infra/ci/compass-ci-job-decomposition/design.md. Refs RIG-2696 Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
Compass engineering docs preview: https://compass-runner-2696-ci-pgtes.compass-eng-docs.pages.dev Deployed from |
Review follow-up: the peeled pgtest job copied the phase-one bootstrap comment verbatim, which still justified an ordering constraint against a phase-two step this job does not have. Trim it to describe pgtest's single-phase (language-toolchains-only) bootstrap accurately. Refs RIG-2696 Co-authored-by: Matt Wilkinson <matt@rigel.build>
This was referenced Aug 25, 2026
mattwilkinsonn
approved these changes
Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is part of a stack containing 5 PRs:
mainMove the real-Postgres suites out of the monolithic
gatesjob into adedicated
pgtestpeer job behind the singleCIrollup, so aPostgres-service flake or the slow
-racesuite no longer serializesbehind the whole moon battery — the two lanes now fail independently and a
service-container flake reds only
pgtest, not the hermetic gate.The postgres service block and both Real-Postgres steps (the suite and its
assert-ran guard) move verbatim; the checkout + install-nix + phase-one
toolchain bootstrap is reproduced (go on PATH is all pgtest needs). The
gatesjob loses its service and two steps and is renamedGates (moon);nothing else in it changes. The
CIrollup gainspgtestinneedsanda third result assertion, so the single required check is unchanged.
pgtest runs unconditionally on every gate event at this step; a later task
gates it on the Go affected-closure so an unaffected PR pays zero.
First task (T1) of the CI job-decomposition plan frozen in
docs/designs/infra/ci/compass-ci-job-decomposition/design.md.
Refs RIG-2696
Co-authored-by: Matt Wilkinson matt@rigel.build