feat(pipeline): balanced splits - #7273
Draft
lemeurherve wants to merge 1 commit into
Draft
Conversation
lemeurherve
force-pushed
the
balanced-splits
branch
6 times, most recently
from
August 14, 2026 08:24
a50a151 to
dd90d24
Compare
lemeurherve
force-pushed
the
balanced-splits
branch
2 times, most recently
from
August 14, 2026 12:35
86b5f2e to
ee34d09
Compare
lemeurherve
force-pushed
the
balanced-splits
branch
13 times, most recently
from
August 15, 2026 20:21
89df095 to
47ea4ea
Compare
6 tasks
lemeurherve
force-pushed
the
balanced-splits
branch
from
August 16, 2026 23:57
47ea4ea to
2a47084
Compare
6 tasks
lemeurherve
force-pushed
the
balanced-splits
branch
4 times, most recently
from
August 17, 2026 10:43
9caa619 to
d678a0e
Compare
lemeurherve
force-pushed
the
balanced-splits
branch
from
August 17, 2026 11:11
d678a0e to
be873a9
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
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 change implements balanced splits using
splitTestsfrom parallel executor plugin extracting splits from junit records of the previous build, to efficiently pack all combinations of repositories and their plugin(s) to get similar pct tests durations across all splits.In case we can't use
splitTestsresults (first build, or tests not executed previously ex: weekly-test label then full-test one), it extracts splits from stored bom reports (#7297).For new repositories that were not in previous junit records or stored bom reports, it will use the previous method from #7256 to distribute them in additional fixed splits.
For the beginning stored bom reports can be updated manually, a future improvement could be to open a pull request on reports when running from
master. (Out of scope for the implementation of balanced splits)With this change, I observed in my builds that
run pctstage take about 35~45mins, versus currently 1h~1h10mins with fixed splits.Ref:
Testing done
Submitter checklist