Skip to content

[CI] MultiClusterSpecIT test {date.Convert no zone} failing #127440

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

Closed
elasticsearchmachine opened this issue Apr 27, 2025 · 1 comment · Fixed by #127453
Closed

[CI] MultiClusterSpecIT test {date.Convert no zone} failing #127440

elasticsearchmachine opened this issue Apr 27, 2025 · 1 comment · Fixed by #127453
Assignees
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

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.Convert no zone}" -Dtests.seed=11C2B69FAD063454 -Dtests.bwc=true -Dtests.locale=he-Hebr-IL -Dtests.timezone=Asia/Gaza -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 failures in test test {date.Convert no zone} (0.9% fail rate in 231 executions)
  • [8.19] 2 failures in step 8.13.4_bwc (50.0% fail rate in 4 executions)
  • [8.19] 2 failures in pipeline elasticsearch-periodic (50.0% fail rate in 4 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 labels Apr 27, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@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 Apr 27, 2025
@idegtiarenko idegtiarenko self-assigned this Apr 28, 2025
@idegtiarenko idegtiarenko added the low-risk An open issue or test failure that is a low risk to future releases label Apr 28, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging a pull request may close this issue.

2 participants