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 {meta.CountFunctions ASYNC} failing #112661

Closed
elasticsearchmachine opened this issue Sep 9, 2024 · 2 comments · Fixed by #112662
Closed

[CI] MixedClusterEsqlSpecIT test {meta.CountFunctions ASYNC} failing #112661

elasticsearchmachine opened this issue Sep 9, 2024 · 2 comments · Fixed by #112662
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

elasticsearchmachine commented Sep 9, 2024

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:mixed-cluster:v8.16.0#javaRestTest" -Dtests.class="org.elasticsearch.xpack.esql.qa.mixed.MixedClusterEsqlSpecIT" -Dtests.method="test {meta.CountFunctions ASYNC}" -Dtests.seed=644904B5974DE683 -Dtests.bwc=true -Dtests.locale=ebu-KE -Dtests.timezone=America/Eirunepe -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 "116" but was "117"
row 0 column 1:a list containing
row 0 column 1:0: expected "116" but was "117"
row 0 column 2:a list containing
row 0 column 2:0: expected "116" but was "117"

Issue Reasons:

  • [main] 3 consecutive failures in test test {meta.CountFunctions ASYNC}
  • [main] 3 consecutive failures in step 8.16.0_bwc-snapshots
  • [main] 5 consecutive failures in pipeline elasticsearch-intake
  • [main] 9 failures in test test {meta.CountFunctions ASYNC} (2.4% fail rate in 382 executions)
  • [main] 9 failures in step 8.16.0_bwc-snapshots (3.5% fail rate in 259 executions)
  • [main] 5 failures in pipeline elasticsearch-intake (7.0% fail rate in 71 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (2.1% fail rate in 194 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 9, 2024
elasticsearchmachine added a commit that referenced this issue Sep 9, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in test test {meta.CountFunctions ASYNC} (1.1% fail rate in 366 executions)
  • [main] 4 failures in step 8.16.0_bwc-snapshots (1.6% fail rate in 250 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (1.6% fail rate in 189 executions)

Build Scans:

@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 Sep 9, 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