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] MixedClusterEsqlSpecIT test {categorize.Categorize SYNC} failing #113722

Open
elasticsearchmachine opened this issue Sep 27, 2024 · 2 comments
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

elasticsearchmachine commented Sep 27, 2024

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:mixed-cluster:v8.17.0#javaRestTest" -Dtests.class="org.elasticsearch.xpack.esql.qa.mixed.MixedClusterEsqlSpecIT" -Dtests.method="test {categorize.Categorize SYNC}" -Dtests.seed=59AF13CA95DCEFE0 -Dtests.bwc=true -Dtests.locale=th-Thai-TH -Dtests.timezone=Europe/Gibraltar -Druntime.java=22

Applicable branches:
8.x

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 "3" but was "1"
row 0 column 1:a list containing
row 0 column 1:0: expected "[Connected to 10.1.0.1, Connected to 10.1.0.2, Connected to 10.1.0.3]" but was "Disconnected"
row 1 column 1:a list containing
row 1 column 1:0: expected "Connection error" but was "[Connected to 10.1.0.1, Connected to 10.1.0.2, Connected to 10.1.0.3]"
row 2 column 0:a list containing
row 2 column 0:0: expected "1" but was "3"
row 2 column 1:a list containing
row 2 column 1:0: expected "Disconnected" but was "Connection error"

Issue Reasons:

  • [8.x] 3 failures in test test {categorize.Categorize SYNC} (0.6% fail rate in 498 executions)
  • [8.x] 3 failures in pipeline elasticsearch-periodic (16.7% fail rate in 18 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 Sep 27, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in test test {categorize.Categorize SYNC} (0.5% fail rate in 795 executions)
  • [main] 3 failures in step 8.16.0_bwc-snapshots (0.8% fail rate in 359 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (1.1% fail rate in 276 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Sep 27, 2024
@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 Sep 27, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this issue Oct 4, 2024
@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 Oct 15, 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 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

No branches or pull requests

3 participants