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 {categorize.Categorize ASYNC} failing #113055

Open
elasticsearchmachine opened this issue Sep 17, 2024 · 7 comments
Open

[CI] EsqlSpecIT test {categorize.Categorize ASYNC} failing #113055

elasticsearchmachine opened this issue Sep 17, 2024 · 7 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 17, 2024

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 {categorize.Categorize ASYNC}" -Dtests.seed=36301A94A4CB8674 -Dtests.locale=ff-Adlm-NG -Dtests.timezone=Africa/Algiers -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] 5 failures in test test {categorize.Categorize ASYNC} (2.6% fail rate in 189 executions)
  • [8.x] 2 failures in step ubuntu-1804_platform-support-unix (50.0% fail rate in 4 executions)
  • [8.x] 4 failures in pipeline elasticsearch-periodic-platform-support (66.7% fail rate in 6 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 17, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in test test {categorize.Categorize ASYNC} (4.2% fail rate in 95 executions)
  • [main] 2 failures in step part-3 (4.8% fail rate in 42 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (4.7% fail rate in 43 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 17, 2024
@astefan astefan 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 Sep 18, 2024
javanna pushed a commit to javanna/elasticsearch that referenced this issue Sep 18, 2024
@jan-elastic
Copy link
Contributor

#113089

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 5 failures in test test {categorize.Categorize ASYNC} (2.3% fail rate in 214 executions)
  • [main] 2 failures in step part3 (6.5% fail rate in 31 executions)
  • [main] 2 failures in step part-3 (1.8% fail rate in 110 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (6.5% fail rate in 31 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.8% fail rate in 110 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This issue has been closed because it has been open for too long with no activity.

Any muted tests that were associated with this issue have been unmuted.

If the tests begin failing again, a new issue will be opened, and they may be muted again.

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test test {categorize.Categorize ASYNC} (7.4% fail rate in 27 executions)
  • [main] 2 failures in step part3 (20.0% fail rate in 10 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (20.0% fail rate in 10 executions)

Build Scans:

jfreden pushed a commit to jfreden/elasticsearch that referenced this issue Nov 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.16

Mute Reasons:

  • [8.16] 2 failures in test test {categorize.Categorize ASYNC} (2.1% fail rate in 94 executions)

Build Scans:

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