Fix flaky test RemoteSegmentTransferTrackerTests.testGetInflightUploadBytes #17128
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.
Description
In
RemoteSegmentTransferTrackerTests.testGetInflightUploadBytes
, we get random value for started, succeeded and failed bytes with following logic:OpenSearch/server/src/test/java/org/opensearch/index/remote/RemoteSegmentTransferTrackerTests.java
Lines 261 to 263 in 46f852a
Here, the expectation is,
started >= failed + succeeded
. We assert with following check:OpenSearch/server/src/main/java/org/opensearch/index/remote/RemoteTransferTracker.java
Lines 257 to 268 in 46f852a
But while assigning random value, it is possible to assign following values which breaks the above assertion:
To make sure the assertion never fails, in this PR, we change the lower bound of started to 12000.
Related Issues
Check List
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.