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 test {lookup-join.LookupMessageFromIndexKeep ASYNC} failing #117976

Closed
elasticsearchmachine opened this issue Dec 4, 2024 · 2 comments · Fixed by #118008
Closed
Labels
:Analytics/ES|QL AKA ESQL needs:risk Requires assignment of a risk label (low, medium, blocker) 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-node:javaRestTest" --tests "org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT" -Dtests.method="test {lookup-join.LookupIPFromIndexKeep ASYNC}" -Dtests.seed=BE0A9C1F9174B2FD -Dtests.locale=fr-MQ -Dtests.timezone=Asia/Riyadh -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 0 column 4:a list containing
row 0 column 4:0: expected "Production" but was "QA"
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 "Production" but was "QA"
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"

Issue Reasons:

  • [main] 3 failures in test test {lookup-join.LookupMessageFromIndexKeep ASYNC} (2.0% fail rate in 149 executions)
  • [main] 2 failures in step part3 (6.9% fail rate in 29 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (6.9% fail rate in 29 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
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test test {lookup-join.LookupMessageFromIndexKeep ASYNC} (2.0% fail rate in 149 executions)
  • [main] 2 failures in step part3 (6.9% fail rate in 29 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (6.9% fail rate in 29 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Dec 4, 2024
@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 Dec 4, 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 needs:risk Requires assignment of a risk label (low, medium, blocker) 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.

1 participant