Shard integration tests by database with on-demand container setup in CI - #6836
Draft
rhcarvalho wants to merge 3 commits into
Draft
Shard integration tests by database with on-demand container setup in CI#6836rhcarvalho wants to merge 3 commits into
rhcarvalho wants to merge 3 commits into
Conversation
rhcarvalho
force-pushed
the
integration-test-ci-database-sharding
branch
from
September 4, 2026 14:36
ee05dc8 to
21f218b
Compare
Contributor
Author
|
This turns the 2 integration test jobs into 8. @SteffenDE your intuition re: Postgres is right, that's the slowest of the shards at 3m23s. |
Contributor
Author
|
The summary also grows from 2 to 8, I don't love that :( |
Contributor
Author
I'll try something that uploads JSON results from each shard as a GitHub artifact (1 day retention, 500 MB limit on the Free plan, we only need a few KB), then aggregates them to produce a single summary. |
…acket Normally the first version we are interested in is the Elixir version, so use `(Elixir <version> | OTP <version>)` pattern across mix test, installer test, and integration test jobs. For integration tests, format the database service as `integration test [<db>] (...)`, labeling the 'none' shard as `[sqlite3 + no-db]` for clarity.
- Update `Phoenix.Integration.SummaryFormatter` to emit JSON artifacts instead of each shard generating a new section to GITHUB_STEP_SUMMARY. - Filter executed test modules in `SummaryFormatter` (reused from PR 6835, credit to Steffen) so modules excluded by database tag do not show up as zero-duration rows or empty Gantt bars. - A fast final step in `ci.yml` waits on all matrix shards to run a script to merge shard JSON summaries into a single, unified GitHub Actions summary.
rhcarvalho
force-pushed
the
integration-test-ci-database-sharding
branch
from
September 4, 2026 16:57
bd06851 to
680177d
Compare
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
1 participant
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.
To compare with #6834 and #6835. Had this locally as I worked through CI improvements this week.