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] EsqlSpecIT class failing #117981

Closed
elasticsearchmachine opened this issue Dec 4, 2024 · 3 comments · Fixed by #118008 or #118136
Closed

[CI] EsqlSpecIT class failing #117981

elasticsearchmachine opened this issue Dec 4, 2024 · 3 comments · Fixed by #118008 or #118136
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 Dec 4, 2024

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:multi-node:javaRestTest" --tests "org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT" -Dtests.method="test {lookup-join.LookupMessageFromIndexKeep SYNC}" -Dtests.seed=50A5FFC4DA6481C4 -Dtests.locale=fr-WF -Dtests.timezone=Asia/Macau -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Data mismatch:
row 0 column 0:a list containing
row 0 column 0:0: expected "2023-10-23T13:55:01.543Z" but was "2023-10-23T12:27:28.948Z"
row 0 column 1:a list containing
row 0 column 1:0: expected "172.21.3.15" but was "172.21.2.113"
row 0 column 2:a list containing
row 0 column 2:0: expected "1756467" but was "2764889"
row 0 column 3:a list containing
row 0 column 3:0: expected "Connected to 10.1.0.1" but was "Connected to 10.1.0.2"
row 1 column 0:a list containing
row 1 column 0:0: expected "2023-10-23T13:53:55.832Z" but was "2023-10-23T12:15:03.360Z"
row 1 column 1:a list containing
row 1 column 1:0: expected "172.21.3.15" but was "172.21.2.162"
row 1 column 2:a list containing
row 1 column 2:0: expected "5033755" but was "3450233"
row 1 column 3:a list containing
row 1 column 3:0: expected "Connection error" but was "Connected to 10.1.0.3"
row 1 column 4:a list containing
row 1 column 4:0: expected "Error" but was "Success"
row 2 column 0:a list containing
row 2 column 0:0: expected "2023-10-23T13:52:55.015Z" but was "2023-10-23T13:55:01.543Z"
row 2 column 2:a list containing
row 2 column 2:0: expected "8268153" but was "1756467"

Issue Reasons:

  • [main] 16 failures in class org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT (1.6% fail rate in 980 executions)
  • [main] 6 failures in step part3 (4.9% fail rate in 122 executions)
  • [main] 10 failures in step part-3 (2.4% fail rate in 415 executions)
  • [main] 6 failures in pipeline elasticsearch-intake (4.9% fail rate in 122 executions)
  • [main] 10 failures in pipeline elasticsearch-pull-request (2.4% fail rate in 414 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 Dec 4, 2024
elasticsearchmachine added a commit that referenced this issue Dec 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in class org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT
  • [main] 2 consecutive failures in step part3
  • [main] 2 consecutive failures in pipeline elasticsearch-intake
  • [main] 15 failures in class org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT (1.5% fail rate in 999 executions)
  • [main] 4 failures in step part3 (3.7% fail rate in 108 executions)
  • [main] 11 failures in step part-3 (2.7% fail rate in 406 executions)
  • [main] 4 failures in pipeline elasticsearch-intake (3.7% fail rate in 108 executions)
  • [main] 11 failures in pipeline elasticsearch-pull-request (2.7% fail rate in 405 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 Dec 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 15 failures in class org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT (1.5% fail rate in 973 executions)
  • [main] 5 failures in step part3 (4.2% fail rate in 120 executions)
  • [main] 10 failures in step part-3 (2.4% fail rate in 410 executions)
  • [main] 5 failures in pipeline elasticsearch-intake (4.2% fail rate in 120 executions)
  • [main] 10 failures in pipeline elasticsearch-pull-request (2.4% fail rate in 409 executions)

Build Scans:

@alex-spies alex-spies 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 Dec 6, 2024
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
2 participants