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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(test runner): improve sharding algorithm to better spread similar tests among shards #30962
feat(test runner): improve sharding algorithm to better spread similar tests among shards #30962
Changes from all commits
54bbba8
ee64b15
6543baf
59c625e
d3b4fad
4bcfc78
061f559
14ca30a
ce09f88
d42c499
b5b8174
389e571
6884fd7
ef2d35f
d33e8da
6b051cb
32169b7
fd90424
c7b58d7
6cf1217
7dd7115
cabfa74
899c068
8aee7df
843d629
2536da7
087a57f
7aa2d95
29f67f3
7b5f7c6
65a2b55
df6d05d
3fed470
050e837
f483ac6
7ea1506
8d485f5
e7273de
1eb11ff
0503672
4b3d754
89458db
7dab70c
b0e5745
5e3fa62
4f758a1
eb25f3c
16b39b8
ea72517
b78b88f
f62651c
07914f7
e7d07bc
412e05b
171c5e1
ad6af69
b3b568b
36433d0
ae34689
4dd2842
ab3ab83
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the comment above about the
round-robin
strategy, I think we should usepartition
when no.last-run.json
is present, and also usepartition
for any tests that were not found in the.last-run.json
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree.
Also please note that
duration-round-robin
and 'round-robin' are using the same implementation. The only difference is that in case of 'duration-round-robin' the last run info is passed to the implementation. However, in case the last run info is passed but it is empty, the behaviour is identical to 'round-robin' where no last run info is passed.I don't think it would be a good to choose a different algorithm based on whether last run info is available or not.