Skip to content

[CI] EsqlClientYamlIT test {p0=esql/10_basic/basic with documents_found} failing #127046

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

Closed
elasticsearchmachine opened this issue Apr 18, 2025 · 3 comments · Fixed by #127065
Closed
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 Apr 18, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:multi-node:yamlRestTest" --tests "org.elasticsearch.xpack.esql.qa.multi_node.EsqlClientYamlIT.test {p0=esql/10_basic/basic with documents_found}" -Dtests.seed=5DAFCB778F792461 -Dtests.locale=saq-Latn-KE -Dtests.timezone=America/Cuiaba -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [esql/10_basic:200]: 
Expected: <10>
     but: was <9>

Issue Reasons:

  • [main] 4 failures in test test {p0=esql/10_basic/basic with documents_found} (0.9% fail rate in 426 executions)
  • [main] 2 failures in step part-3 (2.2% fail rate in 90 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (16.7% fail rate in 12 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.2% fail rate in 89 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 Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 18, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@nik9000 nik9000 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 Apr 18, 2025
@nik9000 nik9000 self-assigned this Apr 18, 2025
nik9000 added a commit to nik9000/elasticsearch that referenced this issue Apr 18, 2025
It was assuming a simpler execution model. This weakens the assertion to
one that should always pass.

Closes elastic#127046
elasticsearchmachine pushed a commit that referenced this issue Apr 21, 2025
It was assuming a simpler execution model. This weakens the assertion to
one that should always pass.

Closes #127046 Closes #127039 Closes #127090 Closes #127080
elasticsearchmachine added a commit that referenced this issue Apr 21, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in test test {p0=esql/10_basic/basic with documents_found} (0.9% fail rate in 426 executions)
  • [main] 2 failures in step part-3 (2.2% fail rate in 90 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (16.7% fail rate in 12 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.2% fail rate in 89 executions)

Build Scans:

@nik9000
Copy link
Member

nik9000 commented Apr 21, 2025

Those failures are PRs that haven't merged the fix.

@nik9000 nik9000 closed this as completed Apr 21, 2025
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

Successfully merging a pull request may close this issue.

2 participants