Repository navigation
Conversation
Code Coverage Report
|
…the aggregate result jobs - Fold the `client` Backend IT shard into `others`. Both are short, and the merged shard still finishes before the slowest build shard, so PR feedback time is unchanged while each backend runs one job less. - Remove `build-result` and `BackendIT-result`. No branch protection rule requires them, so they only added checks.
yuqi1129
marked this pull request as ready for review
September 24, 2026 12:41
Contributor
Author
|
The whole CI can be finished within an hour, but it will add an extra 9 CI pipelines. I'm not sure whether it's worth it.cc @jerryshao |
This was referenced Sep 27, 2026
Collaborator
|
@roryqi @jerryshao PTAL. Efficient CI / Merge Times accelerate OSS development! |
Contributor
Author
|
follow-up: #13471 |
nevzheng
pushed a commit
to nevzheng/gravitino
that referenced
this pull request
Oct 12, 2026
Wire coreUnitTest/coreH2Test/coreMySQLTest/corePostgreSQLTest into a core-test matrix job in build.yml directly, so the PR no longer depends on the Backend IT sharding in apache#13495 (dev/ci/test-shards.sh). The build job skips :core:test and uploads its JaCoCo reports; a coverage job merges them with the four core lane .exec files after core-test-contract reconciles the lanes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019TX7XCnuCMGSJ7xX2iubTH
nevzheng
pushed a commit
to nevzheng/gravitino
that referenced
this pull request
Oct 13, 2026
Wire coreUnitTest/coreH2Test/coreMySQLTest/corePostgreSQLTest into a core-test matrix job in build.yml directly, so the PR no longer depends on the Backend IT sharding in apache#13495 (dev/ci/test-shards.sh). The build job skips :core:test and uploads its JaCoCo reports; a coverage job merges them with the four core lane .exec files after core-test-contract reconciles the lanes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019TX7XCnuCMGSJ7xX2iubTH
nevzheng
self-requested a review
October 21, 2026 16:13
18 tasks
yuqi1129
marked this pull request as draft
October 22, 2026 11:15
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.
What changes were proposed in this pull request?
dev/ci/test-shards.sh, with a catch-allothersshard for new modules.docker,others) and Backend IT (hive,lakehouse,others) shards in parallel matrices; retain main's separate core unit/H2/MySQL/PostgreSQL lanes.Why are the changes needed?
The existing build and Backend IT jobs approach or exceed their 120-minute timeout because Docker-tagged test tasks serialize behind the shared environment lock. Sharding keeps the existing test coverage while shortening the critical path. The measurements and shard plan are in #13459.
Fix: #13459
Does this PR introduce any user-facing change?
No API or configuration changes. CI job names, scheduling, and report artifacts change.
How was this patch tested?
python3 dev/ci/test_test_shards.py, wired into the build workflow: shard ownership, catch-all exclusions, dedicated core lanes, Iceberg experimental tests, complete cron suite, and invalid selectors.bash -n, actionlint, YAML parsing, all 29 shell blocks in the affected workflows, andgit diff --check.