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] MultiClusterSpecIT test {categorize.Categorize} failing #116434

Open
elasticsearchmachine opened this issue Nov 7, 2024 · 2 comments
Open
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-clusters:v8.16.0#bwcTest" -Dtests.class="org.elasticsearch.xpack.esql.ccq.MultiClusterSpecIT" -Dtests.method="test {categorize.Categorize}" -Dtests.seed=8988D753C1815663 -Dtests.bwc=true -Dtests.locale=dje -Dtests.timezone=America/Argentina/San_Luis -Druntime.java=23

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] 2 consecutive failures in step 8.16.0_bwc-snapshots
  • [8.x] 2 failures in test test {categorize.Categorize} (1.6% fail rate in 125 executions)
  • [8.x] 2 failures in step 8.16.0_bwc-snapshots (5.3% fail rate in 38 executions)
  • [8.x] 2 failures in pipeline elasticsearch-intake (8.7% fail rate in 23 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 Nov 7, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 2 consecutive failures in step 8.16.0_bwc-snapshots
  • [8.x] 2 failures in test test {categorize.Categorize} (1.6% fail rate in 125 executions)
  • [8.x] 2 failures in step 8.16.0_bwc-snapshots (5.3% fail rate in 38 executions)
  • [8.x] 2 failures in pipeline elasticsearch-intake (8.7% fail rate in 23 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 Nov 7, 2024
@luigidellaquila luigidellaquila 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 Nov 8, 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

2 participants