ElasticSearchExceptionTests guessRootCauses fix #50752
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
testFailureToAndFromXContentWithDetails had incorporated that guessRootCauses returned the wrapper when the underlying exception was not an ElasticsearchException, fixed. Relates elastic#50525
henningandersen
added
>test
|
Pinging @elastic/es-core-infra (:Core/Infra/Core) |
pugnascotia
approved these changes
Jan 8, 2020
SivagurunathanV
pushed a commit
to SivagurunathanV/elasticsearch
that referenced
this pull request
Jan 23, 2020
testFailureToAndFromXContentWithDetails had incorporated that guessRootCauses returned the wrapper when the underlying exception was not an ElasticsearchException, fixed. Relates elastic#50525
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
testFailureToAndFromXContentWithDetails had incorporated that
guessRootCauses returned the wrapper when the underlying exception
was not an ElasticsearchException, fixed.
Relates #50525
Discovered while backporting #50525, so the fix for this will be incorporated into
the backport of that.