-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Additional trace logging for ESSingleNodeTestCase failures #110790
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
Additional trace logging for ESSingleNodeTestCase failures #110790
Conversation
|
Pinging @elastic/es-search (Team:Search) |
|
@elasticmachine update branch |
carlosdelest
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope you catch that 🐛 !
| } | ||
|
|
||
| protected void putReaderContext(ReaderContext context) { | ||
| logger.trace("adding reader context [{}]", context.id()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want to accidentally merge this into main. The test seems to fail enough that it should be reproducible locally or with this PR if the test is unmuted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm fair enough. Would you be worried of potential impact with this addition?
Tbh, I haven't been lucky locally even after a huge number of runs. Will try to reproduce within this PR :)
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
|
buildkite test this please |
|
buildkite test this please |
|
Closing as a fix for this has been merged through #111153. |
Relates to #110786