-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Unmute CrossClusterEsqlRCS2EnrichUnavailableRemotesIT
#131916
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
Unmute CrossClusterEsqlRCS2EnrichUnavailableRemotesIT
#131916
Conversation
…WithSkipUnavailable` This test got muted due to a build where there were other ES|QL test failures as well. I believe something systematic went wrong with the ES|QL tests and hence the failures. This test itself has been reliable with very few failures and I see no fixes that can be applied.
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
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 think its fine to unmute this one on "main", but looking at the Test Failure History on other branches, there are similar looking failures on other branches (ie. this fairly recent one on 8.19)
Unfortunately I think this will come back at some point, maybe it would be good to add some more logging etc... for more investigation next.
Christoph, if you look at the stack trace, you'll see that the assertion failure is coming from |
…-tracking * upstream/main: (106 commits) Pipelines: Add `created_date` and `modified_date` (elastic#130847) add thread pool change availability (elastic#131734) Add failure store availability info / and port over privileges (elastic#131729) add availability information for ssl handshake timeout settings (elastic#131786) add availability information for rescore_vector (elastic#131710) add availability to oversample value of 0 (elastic#131707) clarify hnsw filter heuristic setting availability (elastic#131715) add availability info for default heap dump path change (elastic#131713) clarify default algorithms per stack version (elastic#131728) Refine error messages in `Fork` for correctness and clarity. (elastic#131701) [ES|QL] Replace RoundTo linear search evaluator with manual evaluators (elastic#131733) ESQL: Fix buildParams in tests with --configuration-cache (elastic#131826) Unmute `CrossClusterEsqlRCS2EnrichUnavailableRemotesIT#testEsqlEnrichWithSkipUnavailable` (elastic#131916) Allow templates for `.chat-*` index template (elastic#131914) ESQL: Fix NPE on empty to_lower/to_upper call (elastic#131917) Fix score computation in ES91Int4VectorsScorer (elastic#131905) Register a blob cache long counter metric for total evicted regions (elastic#131862) Move plan attribute resolution to its own component (elastic#131830) Make restore support multi-project (elastic#131661) Use logically more correct expression (elastic#131869) ...
This test got muted due to a build where there were other ES|QL test failures as well. I believe something systematic went wrong with the ES|QL tests and hence the failures -- where the data received was 0/empty/null across the failures. This test itself has been reliable with very few failures and I see no immediate fixes that can be applied. I'd like to unmute it and see what happens.