-
Notifications
You must be signed in to change notification settings - Fork 24.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
ESQL: Re-enable tests after warnings collection correction #103512
Conversation
Re-enable a couple of warning header checking tests that have been disabled, but mistakenly without linking the issue (elastic#100163), which lead to them being kept disabled also after the fix (elastic#103031).
Pinging @elastic/es-ql (Team:QL) |
Pinging @elastic/elasticsearch-esql (:Query Languages/ES|QL) |
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.
LGTM!
Pinging @elastic/es-analytics-geo (Team:Analytics) |
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.
LGTM
This fails in mixed/multi-node cluster tests b/c the warnings are received from multiple nodes and not deterministically ordered. Will need to adjust the testing infra (possibly introduce regexps). |
It'd be ok with set semantics for warnings. At least, I think so now without much sleep or coffee. |
Re-enable a couple of warning header checking tests that have been disabled, but mistakenly without linking the issue (#100163), which lead to them being kept disabled also after the fix (#103031).