Enable RemoteClusterClientTests#testConnectAndExecuteRequest #101355
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
The test was muted in elastic#97080 without a follow up. Failures are not reproducible anymore, and couldn't find any specific commits from 21.06.2023 that could cause the issue. The only suspicious part from me is that failure logs contain extremely verbose TRACE logs, so there might have been some infra problem causing a node to be unreachable and throwing NodeDisconnectedException
arteam
added
>test
elasticsearchmachine
added
Team:Distributed (Obsolete)
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
idegtiarenko
approved these changes
Oct 26, 2023
arteam
deleted the
enable-remove-cluster-client-tests-connect-and-execute
branch
Contributor
Author
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The test was muted in #97080 without a follow up. Failures are not reproducible anymore, and couldn't find any specific commits from 21.06.2023 that could cause the issue.
The only suspicious part from me is that failure logs contain extremely verbose TRACE logs, so there might have been some infra problem causing a node to be unreachable and throwing NodeDisconnectedException
Fixes #97080