Skip to content

[CI] MixedClusterEsqlSpecIT test {date.Convert no zone SYNC} failing #127293

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 Apr 23, 2025 · 4 comments
Closed

[CI] MixedClusterEsqlSpecIT test {date.Convert no zone SYNC} failing #127293

elasticsearchmachine opened this issue Apr 23, 2025 · 4 comments
Assignees
@not-napoleon
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 Apr 23, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:mixed-cluster:v8.11.4#javaRestTest" -Dtests.class="org.elasticsearch.xpack.esql.qa.mixed.MixedClusterEsqlSpecIT" -Dtests.method="test {date.Convert no zone SYNC}" -Dtests.seed=2F5E2B524F59421C -Dtests.bwc=true -Dtests.locale=ee-GH -Dtests.timezone=US/Central -Druntime.java=24

Applicable branches:
8.19

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Expected an empty list
0: <unexpected> but was "Line 2:13: evaluation of [TO_DATETIME(str)] failed, treating result as null. Only first 20 failures recorded."
1: <unexpected> but was "Line 2:13: java.lang.IllegalArgumentException: failed to parse date field [2025-04-11T05:00:00.000] with format [yyyy-MM-dd'T'HH:mm:ss.SSS'Z']"

Issue Reasons:

  • [8.19] 2 consecutive failures in step 8.11.4_bwc
  • [8.19] 2 consecutive failures in step 8.13.4_bwc
  • [8.19] 12 failures in test test {date.Convert no zone SYNC} (6.7% fail rate in 180 executions)
  • [8.19] 4 failures in step 8.11.4_bwc (44.4% fail rate in 9 executions)
  • [8.19] 3 failures in step 8.13.4_bwc (37.5% fail rate in 8 executions)
  • [8.19] 5 failures in step 8.12.2_bwc (62.5% fail rate in 8 executions)
  • [8.19] 8 failures in pipeline elasticsearch-periodic (88.9% 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 Apr 23, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@fang-xing-esql fang-xing-esql 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 Apr 24, 2025
@nik9000
Copy link
Member

nik9000 commented Apr 24, 2025

@not-napoleon looks like this wasn't supported before 8.13. Want me to skip them back there?

@astefan
Copy link
Contributor

astefan commented Apr 25, 2025

@not-napoleon these tests are pretty fresh in 8.x. Would you mind having a look at them?

@astefan astefan mentioned this issue Apr 25, 2025
Closed
@not-napoleon
Copy link
Member

I believe this is fixed by #127453

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@not-napoleon not-napoleon

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

No branches or pull requests
5 participants
@nik9000 @astefan @not-napoleon @elasticsearchmachine @fang-xing-esql