Repository navigation
ci: build native wheels once and shard the unit and integration tests - #1475
Merged
Merged
Conversation
…ob and three test shards The extension and CLI build once into wheels that the static job and each shard install. check-test-shards, now part of check-ci, proves the shards run every unit and integration test exactly once, using the shard coverage check the DuckDB E2E shards already had. On a Release Please version-bump head, Lockfile consistency waits for the lockfile refresh commit, whose run checks the lockfiles. The depth step documents that re-running an older Verify suite never repaints the required check.
…ease lockfile wait
kvlonge
marked this pull request as ready for review
November 14, 2026 09:47
kvlonge
enabled auto-merge
November 14, 2026 09:50
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
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.
Why
"Static checks and unit + integration tests" is the slowest job on every pull request's critical path: about 31–35 minutes on one runner, spent as a 9-minute native build, 2–3 minutes of static checks and 18–22 minutes of tests on 2 xdist workers. One file, the warehouse history publication tests, takes about 15 minutes of that serial time.
Changes
native_buildjob builds the extension and CLI wheels once. Achecksjob (make check-ci) and three test shards install those wheels instead of compiling:publication/;publication/except the warehouse history tests;test_warehouse_metadata.py, spread test by test (--dist load).check-test-shards, now incheck-ci, fails when a unit or integration test is in no shard or in two. It generalises the DuckDB E2E shard check, which keeps its behaviour.make testis unchanged.Verifyrequires the new jobs exactly as it required the old one.Verification
make check-cipasses; shard coverage 12,225 tests (core 12,032, publication 145, history 48); E2E 2,641.owners: none; dropping the publication--ignorefails with two owners.DuckShop: not applicable; this changes CI job layout only.