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.

Sign up for GitHub

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

Jump to bottom

[CI] EsqlActionBreakerIT class failing #122810

Open
elasticsearchmachine opened this issue Feb 18, 2025 · 3 comments
Open

[CI] EsqlActionBreakerIT class failing #122810

elasticsearchmachine opened this issue Feb 18, 2025 · 3 comments
Assignees
@dnhatn
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:internalClusterTest" --tests "org.elasticsearch.xpack.esql.action.EsqlActionBreakerIT.testFromStatsGroupingAvg" -Dtests.seed=5B781C0629C87C8F -Dtests.jvm.argline="-Des.entitlements.enabled=true" -Dtests.locale=bho -Dtests.timezone=Australia/Broken_Hill -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Request breaker not reset to 0 on node: node_s1
Expected: <0L>
     but: was <96L>

Issue Reasons:

  • [main] 4 failures in class org.elasticsearch.xpack.esql.action.EsqlActionBreakerIT (0.4% fail rate in 944 executions)
  • [main] 3 failures in step part-3 (1.0% fail rate in 306 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (1.0% fail rate in 315 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :StorageEngine/Mapping The storage related side of mappings >test-failure Triaged test failures from CI labels Feb 18, 2025
elasticsearchmachine added a commit that referenced this issue Feb 18, 2025
@elasticsearchmachine
Mute org.elasticsearch.xpack.esql.action.EsqlActionBreakerIT org.elas…
19fe0a4 
…ticsearch.xpack.esql.action.EsqlActionBreakerIT #122810
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in class org.elasticsearch.xpack.esql.action.EsqlActionBreakerIT (0.4% fail rate in 944 executions)
  • [main] 3 failures in step part-3 (1.0% fail rate in 306 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (1.0% fail rate in 315 executions)

Build Scans:

@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@elasticsearchmachine elasticsearchmachine added the needs:risk Requires assignment of a risk label (low, medium, blocker) label Feb 18, 2025
@dnhatn dnhatn self-assigned this Feb 18, 2025
@dnhatn dnhatn added low-risk An open issue or test failure that is a low risk to future releases :Analytics/ES|QL AKA ESQL and removed needs:risk Requires assignment of a risk label (low, medium, blocker) :StorageEngine/Mapping The storage related side of mappings labels Feb 18, 2025
@elasticsearchmachine elasticsearchmachine added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) and removed Team:StorageEngine labels Feb 18, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

This was referenced Feb 20, 2025
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dnhatn dnhatn

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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dnhatn @elasticsearchmachine