Skip to content
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

[CI] MultiClusterSpecIT test {date.IN operator with null in list, doesn't find match} failing #120348

Closed
elasticsearchmachine opened this issue Jan 17, 2025 · 3 comments
Assignees
Labels
:Analytics/ES|QL AKA ESQL medium-risk An open issue or test failure that is a medium 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 Jan 17, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:multi-clusters:v8.13.4#oldToNew" -Dtests.class="org.elasticsearch.xpack.esql.ccq.MultiClusterSpecIT" -Dtests.method="test {date.IN operator with null in list, doesn't find match}" -Dtests.seed=ED4032AA8E32DF54 -Dtests.bwc=true -Dtests.locale=rn -Dtests.timezone=Europe/Sofia -Druntime.java=23

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Expected an empty list
0: <unexpected> but was "Line 3:24: evaluation of [TO_DATETIME(\\\"1900-02-19T00:00:00Z\\\")] failed, treating result as null. Only first 20 failures recorded."
1: <unexpected> but was "Line 3:24: java.lang.IllegalArgumentException: failed to parse date field [1900-02-19T00:00:00Z] with format [yyyy-MM-dd'T'HH:mm:ss.SSS'Z']"

Issue Reasons:

  • [8.x] 11 failures in test test {date.IN operator with null in list, doesn't find match} (1.2% fail rate in 952 executions)
  • [8.x] 11 failures in step 8.13.4_bwc (100.0% fail rate in 11 executions)
  • [8.x] 9 failures in pipeline elasticsearch-periodic (100.0% fail rate in 9 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Analytics/ES|QL AKA ESQL >test-failure Triaged test failures from CI Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 17, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

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

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 11 failures in test test {date.IN operator with null in list, doesn't find match} (1.2% fail rate in 952 executions)
  • [8.x] 11 failures in step 8.13.4_bwc (100.0% fail rate in 11 executions)
  • [8.x] 9 failures in pipeline elasticsearch-periodic (100.0% fail rate in 9 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Jan 21, 2025
…N operator with null in list, doesn't find match} #120348
not-napoleon added a commit that referenced this issue Jan 22, 2025
Resolves #120159
Resolves #120157
Resolves #120151
Resolves #120158
Resolves #120155
Resolves #120156
Resolves #120348
Resolves #120349

This adds appropriate ignore annotations for the date tests I added in #119772 to not run the tests against very old versions.
@not-napoleon
Copy link
Member

Resolved by #120543

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL medium-risk An open issue or test failure that is a medium 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
Development

No branches or pull requests

3 participants