-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 testCorruptedTranslog test #9139
Conversation
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Signed-off-by: Daniel Widdis <widdis@gmail.com>
Compatibility status:
|
Compatibility status:
|
Gradle Check (Jenkins) Run Completed with:
|
Compatibility status:
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## main #9139 +/- ##
============================================
- Coverage 71.06% 71.05% -0.01%
+ Complexity 57314 57293 -21
============================================
Files 4766 4765 -1
Lines 270453 270478 +25
Branches 39555 39552 -3
============================================
- Hits 192197 192192 -5
- Misses 62045 62072 +27
- Partials 16211 16214 +3
|
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-9139-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f9c728f4f2d50c5d020f46a8658d1a79113bc19e
# Push it to GitHub
git push --set-upstream origin backport/backport-9139-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x Then, create a pull request where the |
Looked into manual backporting and see the impacted line is 3.x only, so removed backport tag. |
* Fix flaky testCorruptedTranslog test Signed-off-by: Daniel Widdis <widdis@gmail.com> * Simplify by allowing different wrapped exception Signed-off-by: Daniel Widdis <widdis@gmail.com> * Remove unnecessary parens: || higher precedence than instanceof Signed-off-by: Daniel Widdis <widdis@gmail.com> --------- Signed-off-by: Daniel Widdis <widdis@gmail.com> Signed-off-by: Kaushal Kumar <ravi.kaushal97@gmail.com>
* Fix flaky testCorruptedTranslog test Signed-off-by: Daniel Widdis <widdis@gmail.com> * Simplify by allowing different wrapped exception Signed-off-by: Daniel Widdis <widdis@gmail.com> * Remove unnecessary parens: || higher precedence than instanceof Signed-off-by: Daniel Widdis <widdis@gmail.com> --------- Signed-off-by: Daniel Widdis <widdis@gmail.com> Signed-off-by: Ivan Brusic <ivan.brusic@flocksafety.com>
* Fix flaky testCorruptedTranslog test Signed-off-by: Daniel Widdis <widdis@gmail.com> * Simplify by allowing different wrapped exception Signed-off-by: Daniel Widdis <widdis@gmail.com> * Remove unnecessary parens: || higher precedence than instanceof Signed-off-by: Daniel Widdis <widdis@gmail.com> --------- Signed-off-by: Daniel Widdis <widdis@gmail.com> Signed-off-by: Shivansh Arora <hishiv@amazon.com>
Description
The
RemoveCorruptedShardDataCommandTests
tests for appropriate exceptions on corrupted translogs. In the rare edge case where the corruption occurs in the header where the UUID tracks the engine, the expectedTranslogCorruptedException
is caught and rethrown as anEngineCreationFailureException
rather than theTranslogException
expected by the test.This change relaxes the test to allow either wrapped exception while testing the same cause.
Related Issues
Fixes #6179
Command reproducing this failure at linked issue; this test passes after this fix.
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.