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] EsqlActionBreakerIT testExtractFields failing #122125

Closed
elasticsearchmachine opened this issue Feb 8, 2025 · 3 comments
Closed

[CI] EsqlActionBreakerIT testExtractFields failing #122125

elasticsearchmachine opened this issue Feb 8, 2025 · 3 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

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:internalClusterTest" --tests "org.elasticsearch.xpack.esql.action.EsqlActionBreakerIT.testExtractFields" -Dtests.seed=B3575A018EA0ACD -Dtests.locale=teo-KE -Dtests.timezone=IST -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: an instance of org.elasticsearch.common.breaker.CircuitBreakingException
     but: <org.elasticsearch.action.NoShardAvailableActionException: CurrentState[RECOVERING] operations only allowed when shard state is one of [POST_RECOVERY, STARTED]> is a org.elasticsearch.action.NoShardAvailableActionException

Issue Reasons:

  • [main] 2 failures in test testExtractFields (11.1% fail rate in 18 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testExtractFields (11.1% fail rate in 18 executions)

Build Scans:

@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 Feb 8, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@dnhatn dnhatn 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 Feb 8, 2025
@dnhatn dnhatn self-assigned this Feb 8, 2025
@dnhatn
Copy link
Member

dnhatn commented Feb 10, 2025

Close in favor of #122153

@dnhatn dnhatn closed this as completed Feb 10, 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

No branches or pull requests

2 participants