[CI] RemoteSearchForceConnectTimeoutIT testTimeoutSetting failing #131656
Description
Build Scans:
- elasticsearch-intake #25937 / part1
- elasticsearch-pull-request #82271 / part-1
- elasticsearch-periodic-platform-support #9521 / windows-2025_checkpart1_platform-support-windows
- elasticsearch-periodic #9510 / openjdk21_checkpart1_java-matrix
- elasticsearch-periodic #9510 / openjdk21_checkpart1_java-fips-matrix
- elasticsearch-periodic #9510 / openjdk23_checkpart1_java-matrix
- elasticsearch-periodic-platform-support #9521 / debian-12_platform-support-unix
- elasticsearch-periodic-platform-support #9521 / sles-15_platform-support-unix
- elasticsearch-periodic-platform-support #9521 / rocky-9_platform-support-unix
- elasticsearch-pull-request #81994 / part-1
Reproduction Line:
./gradlew ":server:internalClusterTest" --tests "org.elasticsearch.indices.cluster.RemoteSearchForceConnectTimeoutIT.testTimeoutSetting" -Dtests.seed=9568DF993389FEDF -Dtests.locale=szl-PL -Dtests.timezone=America/Grand_Turk -Druntime.java=24
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
java.lang.AssertionError:
Expected: <1>
but: was <0>
Issue Reasons:
- [main] 2 consecutive failures in test testTimeoutSetting
- [main] 12 failures in test testTimeoutSetting (24.0% fail rate in 50 executions)
- [main] 2 failures in step part1 (33.3% fail rate in 6 executions)
- [main] 3 failures in step part-1 (16.7% fail rate in 18 executions)
- [main] 2 failures in pipeline elasticsearch-intake (33.3% fail rate in 6 executions)
- [main] 3 failures in pipeline elasticsearch-pull-request (18.8% fail rate in 16 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.