-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[META] Eliminate flakiness in :server:internalClusterTest
#18108
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
Comments
Results for April 24 (c5e55b0)Success rate:34% (44 out of 128) Failed tests
Actions
|
Results for April 30 (0795bb2)Success rate:70% (30 out of 43) Failed tests
Actions
|
Results for May 1 (0cbd848)Success rate:92% (34 out of 37, progress!) Failed tests
Actions |
Results for May 6 (c32262d)Success rate:75% (30 out of 40) Failed tests
Actions
|
Results for May 14 (998ae73)Success rate:71% (27 out of 38) Failed tests
Actions
|
Results for May 15 (20d56d2)Success rate:72% (31 of 43) Failed tests
Actions
|
Hey @andrross, I've implemented the same setup. Looks like the runs will take several hours. Will automate this action through a jenkins job where we could get the list of failed tests after all iterations once the job runs successfully. And eventually we can ingest the data to the metrics cluster. Will tag the related issues once created. |
@Divyaasm A successful run of |
Results for May 21 (d723db8)Success rate:68% (25 of 37) Failed tests
Actions
|
Yes my estimate is it could take a couple of days. We can make the number of iterations flexible as per our requirement before we trigger the job. |
Should we test with the |
Uh oh!
There was an error while loading. Please reload this page.
Please describe the end goal of this project
We have no shortage of issues related to flaky tests. I'm creating this new issue with a more narrow focus (only
:server:internalClusterTest
) and specific goal (eliminate current flakiness). The intent is to get the most problematic flakiness back under control to make merging PRs a less miserable experience, while we continue to iterate on new mechanisms in #17974Supporting References
Flakiness of
:server:internalClusterTest
is simple to measure, and I'll continue posting updates on this issue to track progress.Test Environment:
Test procedure:
Count failures:
Count number of runs:
Display test failures by count:
Issues
Related to #17974
Related component
Build
The text was updated successfully, but these errors were encountered: