-
Notifications
You must be signed in to change notification settings - Fork 25.6k
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-periodic #6759 / single-processor-node-tests
- elasticsearch-periodic #6745 / single-processor-node-tests
Reproduction Line:
./gradlew ":test:external-modules:test-esql-heap-attack:javaRestTest" --tests "org.elasticsearch.xpack.esql.heap_attack.HeapAttackIT.testEnrichExplosionManyMatches" -Dtests.seed=25F269D7FF8C8AC1 -Dtests.configure_test_clusters_with_one_processor=true -Dtests.locale=cv-RU -Dtests.timezone=America/Cayenne -Druntime.java=23
Applicable branches:
8.x
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
java.net.ConnectException: Connection refused
Issue Reasons:
- [8.x] 2 failures in test testSortByManyLongsSuccess (2.0% fail rate in 101 executions)
- [8.x] 2 failures in step single-processor-node-tests (50.0% fail rate in 4 executions)
- [8.x] 2 failures in pipeline elasticsearch-periodic (50.0% fail rate in 4 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Metadata
Metadata
Assignees
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