Skip to content
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

Fix flaky test testDownloadStatsCorrectnessSinglePrimarySingleReplica #14646

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

skumawat2025
Copy link
Contributor

@skumawat2025 skumawat2025 commented Jul 4, 2024

Flaky test testDownloadStatsCorrectnessSinglePrimarySingleReplica is not repro after 5k+ iteration on single test and suite level runs. This test is failing with AssertError and not reproducible locally. There is no assertBusy for zeroStats assertions, adding it now. Test logging is already enabled on this.

In one of the failures this test is failing at this line:

Description

[Describe what this change achieves]

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • [ ] Functionality includes testing.
  • [ ] API changes companion pull request created, if applicable.
  • [ ] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Contributor

github-actions bot commented Jul 4, 2024

✅ Gradle check result for 17c33d0: SUCCESS

Copy link

codecov bot commented Jul 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.72%. Comparing base (6b8b3ef) to head (126f7d5).
Report is 146 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #14646      +/-   ##
============================================
- Coverage     71.82%   71.72%   -0.10%     
+ Complexity    62467    62375      -92     
============================================
  Files          5149     5149              
  Lines        293396   293396              
  Branches      42392    42392              
============================================
- Hits         210725   210441     -284     
- Misses        65245    65546     +301     
+ Partials      17426    17409      -17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

&& zeroStatePrimaryStats.uploadBytesSucceeded > 0
);
assertTrue(zeroStatePrimaryStats.totalUploadsFailed == 0 && zeroStatePrimaryStats.uploadBytesFailed == 0);
}, 60, TimeUnit.SECONDS);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's reduce the assertBusy wait time. Ideally the default value of this method should suffice, let's remove the extra time value we are adding to this assertBusy invocation

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. Keeping the default value of asserBusy() which is 10 seconds.

@skumawat2025 skumawat2025 added Storage:Remote flaky-test Random test failure that succeeds on second run labels Jul 12, 2024
Copy link
Contributor

✅ Gradle check result for 126f7d5: SUCCESS

Copy link
Member

@shourya035 shourya035 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ashking94
Copy link
Member

@skumawat2025 Are you able to reproduce this locally? If so, after how many iterations?

@skumawat2025
Copy link
Contributor Author

skumawat2025 commented Jul 12, 2024

@skumawat2025 Are you able to reproduce this locally? If so, after how many iterations?

No Ashish, this did not repro after 5k+ iteration of single test and suit level test runs. But as we are seeing the assertion failures at this line specifically, It is highly possible that the issues is with zero stats assertion statements. I've included these details in the PR description as well.

@opensearch-trigger-bot
Copy link
Contributor

This PR is stalled because it has been open for 30 days with no activity.

@opensearch-trigger-bot opensearch-trigger-bot bot added the stalled Issues that have stalled label Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Random test failure that succeeds on second run skip-changelog stalled Issues that have stalled Storage:Remote
Projects
Status: 🏗 In progress
Development

Successfully merging this pull request may close these issues.

3 participants