-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Closed
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>test-failureTriaged test failures from CITriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)low-riskAn open issue or test failure that is a low risk to future releasesAn open issue or test failure that is a low risk to future releases
Description
Build Scans:
- elasticsearch-intake #25576 / part3
- elasticsearch-periodic #9376 / release-tests
- elasticsearch-periodic #9369 / release-tests
Reproduction Line:
./gradlew ":x-pack:plugin:esql:internalClusterTest" --tests "org.elasticsearch.xpack.esql.action.CrossClusterAsyncQueryStopIT.testStopQuery" -Dtests.seed=F3E498874ABA4D1C -Dtests.locale=de-CH -Dtests.timezone=America/Yellowknife -Druntime.java=24
Applicable branches:
9.1
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
java.lang.AssertionError: Request breaker not reset to 0 on node: main-cluster-0
Expected: <0L>
but: was <32L>
Issue Reasons:
- [9.1] 2 consecutive failures in step release-tests
- [9.1] 3 failures in test testStopQueryLocal (4.2% fail rate in 71 executions)
- [9.1] 2 failures in step release-tests (100.0% fail rate in 2 executions)
- [9.1] 2 failures in pipeline elasticsearch-periodic (100.0% fail rate in 2 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Metadata
Metadata
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>test-failureTriaged test failures from CITriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)low-riskAn open issue or test failure that is a low risk to future releasesAn open issue or test failure that is a low risk to future releases