Skip to content

[CI] PushQueriesIT testEqualityAndOther {semantic_text} failing #128414

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.

Sign up for GitHub

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

Jump to bottom
Closed
elasticsearchmachine opened this issue May 23, 2025 · 4 comments · Fixed by #128434
Closed

[CI] PushQueriesIT testEqualityAndOther {semantic_text} failing #128414

elasticsearchmachine opened this issue May 23, 2025 · 4 comments · Fixed by #128434
Assignees
@iverase
Labels
:Analytics/ES|QL AKA ESQL low-risk An open issue or test failure that is a low risk to future releases Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented May 23, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:single-node:javaRestTest" --tests "org.elasticsearch.xpack.esql.qa.single_node.PushQueriesIT.testEqualityAndOther {semantic_text}" -Dtests.seed=68B29CC0BA6B855F -Dtests.locale=en-MW -Dtests.timezone=America/Edmonton -Druntime.java=24

Applicable branches:
8.19

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Expected a map containing
             operator: "LuceneSourceOperator[maxPageSize = 4854, remainingDocs = 2147483646]"
               status: a map containing
      processed_queries: a list containing
                        0: expected ("#(#foo:[1 TO 1] #single_value_match(foo)) #FieldExistsQuery [field=_primary_term]" or "foo:[1 TO 1]") but was "#foo:[1 TO 1] #FieldExistsQuery [field=_primary_term]"
       processed_slices: <1> unexpected but ok
       processed_shards: <[test:0]> unexpected but ok
           total_slices: <1> unexpected but ok
              slice_max: <0> unexpected but ok
                current: <2147483647> unexpected but ok
              slice_min: <0> unexpected but ok
           rows_emitted: <1> unexpected but ok
          pages_emitted: <1> unexpected but ok
partitioning_strategies: <{test:0=SHARD}> unexpected but ok
       processing_nanos: <392695> unexpected but ok
            slice_index: <0> unexpected but ok

Issue Reasons:

  • [8.19] 3 failures in test testEqualityAndOther {semantic_text} (0.9% fail rate in 352 executions)
  • [8.19] 2 failures in pipeline elasticsearch-periodic-platform-support (20.0% fail rate in 10 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added >test-failure Triaged test failures from CI :Analytics/ES|QL AKA ESQL labels May 23, 2025
elasticsearchmachine added a commit that referenced this issue May 23, 2025
@elasticsearchmachine
Mute org.elasticsearch.xpack.esql.qa.single_node.PushQueriesIT testEq…
80a41a7 
…ualityAndOther {semantic_text} #128414
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 8 failures in test testEqualityAndOther {semantic_text} (0.9% fail rate in 844 executions)
  • [main] 5 failures in step part-3 (1.4% fail rate in 351 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (12.5% fail rate in 16 executions)
  • [main] 5 failures in pipeline elasticsearch-pull-request (1.4% fail rate in 351 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels May 23, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-analytical-engine (Team:Analytics)

@iverase iverase self-assigned this May 24, 2025
@iverase
Copy link
Contributor

iverase commented May 24, 2025

related to #128293

@iverase iverase added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels May 24, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.19

Mute Reasons:

  • [8.19] 3 failures in test testEqualityAndOther {semantic_text} (0.9% fail rate in 352 executions)
  • [8.19] 2 failures in pipeline elasticsearch-periodic-platform-support (20.0% fail rate in 10 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue May 26, 2025
@elasticsearchmachine
Mute org.elasticsearch.xpack.esql.qa.single_node.PushQueriesIT testEq…
deb0e61 
…ualityAndOther {semantic_text} #128414
@iverase iverase mentioned this issue May 26, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iverase iverase

Labels
:Analytics/ES|QL AKA ESQL low-risk An open issue or test failure that is a low risk to future releases Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adjust generated pushdown query for IndexOrDocValuesQuery iverase/elasticsearch
2 participants
@iverase @elasticsearchmachine