Skip to content

ci: verify the full matrix once in the merge queue and tier timing jobs - #1460

Merged
chio-labs-delivery[bot] merged 2 commits into
mainfrom
ci/faster-pr-checks
Nov 14, 2026
Merged

chio-labs-delivery[bot] merged 2 commits into
mainfrom
ci/faster-pr-checks

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Why

A typical pull request waits on the whole matrix twice: once for the label run, and again when it merges. Release pull requests rerun every suite, even though they change only version lines. The 5k/10k-model timing jobs and four of five wheel platforms add most of the wall time.

Changes

  • build-distributions.yml takes a platforms input. Verify builds only the linux-x86_64 wheel on pull requests and merge groups. Scheduled and manual runs, Release Distributions and Publish still build all five.
  • When the SQLBUILD_MERGE_QUEUE variable is true, a passing fast core on a pull request reports as Verify, and every merge group runs the full matrix once before merging.
  • A merge group whose whole diff is release metadata (exact version lines only) skips the suites. The lockfile check still runs.
  • Pull requests and merge groups run the cold and cache compile jobs at 3k models and the dense job at 1k and 3k.
  • A nightly run on main adds the 5k and 10k jobs and every wheel platform, and opens or updates a nightly-verify issue when it fails.
  • Changes confined to the orchestration and CLI Rust test crates run native checks and the recovery suite.

After merge, someone with admin access sets the repository variable SQLBUILD_MERGE_QUEUE=true. The main ruleset already has the merge queue.

Verification

  • I replayed the scope classifier over the last 40 merged commits. All 13 release pull requests select no suites as merge groups. A server test-only change selects only checks and recovery. Everything else selects the same suites as before.
  • I ran the platform filter locally for empty, single, padded and unknown names, with the cache writer on and off.
  • actionlint reports only the two errors already on main. check_release_gate passes, as do its 47 tests.
  • One independent review; its findings are fixed.

DuckShop: not applicable. This changes CI only, not the compiler or project behaviour.

… groups

Work in progress, first of five planned CI speed-ups. Not yet opened as a
pull request.

build-distributions.yml takes a platforms input; its source job filters the
one platform list into the wheel matrix and rejects unknown names. Verify
passes linux-x86_64 on pull requests and merge groups, which Compose needs;
manual runs and Release Distributions still build every platform.

Validated: the filter script run locally for an empty selection (all five),
one platform, two platforms and an unknown name (fails); both workflows parse
as YAML; make check-release-gate passes. Not yet run in GitHub Actions.
A passing fast core reports as Verify when the repository variable
SQLBUILD_MERGE_QUEUE is true, because the merge queue runs the full matrix
on every group before it merges. A merge group whose whole diff is release
metadata skips the suites, as release pull requests already do.

Pull requests and merge groups run the 3k-model compile jobs and the 1k
dense job; a nightly scheduled run on main adds 5k and 10k and every
wheel platform, and opens or updates an issue when it fails. Changes to
the orchestration and CLI Rust test crates run native checks and the
scheduler recovery suite instead of every suite.
@kvlonge kvlonge added the full-verify Run the full Verify matrix on this pull request label Nov 13, 2026
@chio-labs-delivery
chio-labs-delivery Bot added this pull request to the merge queue Nov 13, 2026
Merged via the queue into main with commit fd2dcc6 Nov 14, 2026
38 of 60 checks passed
@chio-labs-delivery
chio-labs-delivery Bot deleted the ci/faster-pr-checks branch November 14, 2026 00:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-verify Run the full Verify matrix on this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant