Unmute CrossClusterEsqlRCS2EnrichUnavailableRemotesIT
#131916
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
…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.
pawankartik-elastic
added
Team:Search Foundations
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
cbuescher
approved these changes
Jul 25, 2025
There was a problem hiding this comment.
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 |
pawankartik-elastic
deleted the
pkar/unmute-CrossClusterEsqlRCS2EnrichUnavailableRemotesIT
branch
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Jul 25, 2025
…-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) ...
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.
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.