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.

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

[CI] EsqlSpecIT test {stats.MaxOfIpGrouping SYNC} failing #111136

Closed
elasticsearchmachine opened this issue Jul 20, 2024 · 2 comments · Fixed by #111149
Closed

[CI] EsqlSpecIT test {stats.MaxOfIpGrouping SYNC} failing #111136

elasticsearchmachine opened this issue Jul 20, 2024 · 2 comments · Fixed by #111149
Assignees
@ivancea
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-node:javaRestTest" --tests "org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT" -Dtests.method="test {stats.MaxOfIpGrouping SYNC}" -Dtests.seed=16531E6370D07029 -Dtests.locale=es-VE -Dtests.timezone=Pacific/Samoa -Druntime.java=22

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 "127.0.0.1" but was "fe82::cae2:65ff:fece:fec0"
row 0 column 1:a list containing
row 0 column 1:0: expected "127.0.0.1" but was "fe82::cae2:65ff:fece:fec0"
row 0 column 2:a list containing
row 0 column 2:0: expected "127.0.0.1" but was "fe82::cae2:65ff:fece:fec0"
row 0 column 3:a list containing
row 0 column 3:0: expected "127.0.0.1" but was "fe82::cae2:65ff:fece:fec0"
row 0 column 4:a list containing
row 0 column 4:0: expected "beta" but was "epsilon"
row 1 column 0:a list containing
row 1 column 0:0: expected "fe80::cae2:65ff:fece:feb9" but was "127.0.0.1"
row 1 column 1:a list containing
row 1 column 1:0: expected "fe80::cae2:65ff:fece:feb9" but was "127.0.0.1"
row 1 column 2:a list containing
row 1 column 2:0: expected "fe80::cae2:65ff:fece:feb9" but was "127.0.0.1"
row 1 column 3:a list containing
row 1 column 3:0: expected "fe81::cae2:65ff:fece:feb9" but was "127.0.0.1"
row 1 column 4:a list containing
row 1 column 4:0: expected "gamma" but was "beta"
row 2 column 0:a list containing
row 2 column 0:0: expected "fe82::cae2:65ff:fece:fec0" but was "fe80::cae2:65ff:fece:feb9"

Issue Reasons:

  • [main] 3 failures in test test {stats.MaxOfIpGrouping SYNC} (2.2% fail rate in 137 executions)
  • [main] 2 failures in step part-3 (6.9% fail rate in 29 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (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 Jul 20, 2024
elasticsearchmachine added a commit that referenced this issue Jul 20, 2024
@elasticsearchmachine
Mute org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT test {stat…
4a20518 
…s.MaxOfIpGrouping SYNC} #111136
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test test {stats.MaxOfIpGrouping SYNC} (2.2% fail rate in 137 executions)
  • [main] 2 failures in step part-3 (6.9% fail rate in 29 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (6.9% fail rate in 29 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 Jul 20, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

This was referenced Jul 22, 2024
Closed
Closed
Closed
Closed
@ivancea ivancea mentioned this issue Jul 22, 2024
Merged
@ivancea ivancea 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 Jul 22, 2024
ioanatia pushed a commit to ioanatia/elasticsearch that referenced this issue Jul 22, 2024
@elasticsearchmachine @ioanatia
Mute org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT test {stat…
dd9a93f 
…s.MaxOfIpGrouping SYNC} elastic#111136
salvatore-campagna pushed a commit to salvatore-campagna/elasticsearch that referenced this issue Jul 23, 2024
@elasticsearchmachine @salvatore-campagna
Mute org.elasticsearch.xpack.esql.qa.multi_node.EsqlSpecIT test {stat…
df31d5f 
…s.MaxOfIpGrouping SYNC} elastic#111136
salvatore-campagna pushed a commit to salvatore-campagna/elasticsearch that referenced this issue Jul 23, 2024
@ivancea @salvatore-campagna
ESQL: Unmute and fix Max/Min CSV tests with unsorted IPs (elastic#111149
6cb3788 
)

Fixes elastic#111107
Fixes elastic#111125
Fixes elastic#111136
Fixes elastic#111137
Fixes elastic#111138
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ivancea ivancea

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

Successfully merging a pull request may close this issue.

ESQL: Unmute and fix Max/Min CSV tests with unsorted IPs ivancea/elasticsearch
2 participants
@ivancea @elasticsearchmachine