[CI] DocsClientYamlTestSuiteIT class failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-intake #16068 / part1
• elasticsearch-pull-request #51440 / part-1
• elasticsearch-pull-request #51440 / part-1-fips
• elasticsearch-pull-request #51425 / part-1
• elasticsearch-pull-request #51425 / part-1-fips
• elasticsearch-pull-request #51386 / part-1-fips
• elasticsearch-pull-request #51386 / part-1
• elasticsearch-pull-request #51339 / part-1
• elasticsearch-pull-request #51339 / part-1-fips
• elasticsearch-pull-request #51151 / part-1

Reproduction Line:

./gradlew ":docs:yamlRestTest" --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/aggregations/metrics/median-absolute-deviation-aggregation/line_90}" -Dtests.seed=6C9BF90A87682AF9 -Dtests.locale=su-Latn-ID -Dtests.timezone=America/Matamoros -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.RuntimeException: Failure at [reference/aggregations/metrics/median-absolute-deviation-aggregation:80]: Connection refused

Issue Reasons:

• [main] 22 failures in class org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT (2.2% fail rate in 988 executions)
• [main] 14 failures in step part-1 (3.4% fail rate in 410 executions)
• [main] 6 failures in step part-1-fips (50.0% fail rate in 12 executions)
• [main] 15 failures in pipeline elasticsearch-pull-request (3.6% fail rate in 413 executions)

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

[elasticsearchmachine]

This has been muted on branch main

Mute Reasons:

• [main] 22 failures in class org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT (2.2% fail rate in 988 executions)
• [main] 14 failures in step part-1 (3.4% fail rate in 410 executions)
• [main] 6 failures in step part-1-fips (50.0% fail rate in 12 executions)
• [main] 15 failures in pipeline elasticsearch-pull-request (3.6% fail rate in 413 executions)

Build Scans:

• elasticsearch-intake #16068 / part1
• elasticsearch-pull-request #51440 / part-1
• elasticsearch-pull-request #51440 / part-1-fips
• elasticsearch-pull-request #51425 / part-1
• elasticsearch-pull-request #51425 / part-1-fips
• elasticsearch-pull-request #51386 / part-1-fips
• elasticsearch-pull-request #51386 / part-1
• elasticsearch-pull-request #51339 / part-1
• elasticsearch-pull-request #51339 / part-1-fips
• elasticsearch-pull-request #51151 / part-1

[elasticsearchmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[nielsbauman]

All the failing PR builds are caused by the PR themselves (i.e. the PRs introduced code that made certain tests related to that code fail) and the only non-PR build doesn't seem to have a concrete failure cause -- I'm only seeing a bunch of timeouts and refused connections. I didn't dive very deep into why the connections were dropped (probably dropping nodes) but since it was only one instance, I'm going to label this as a infra blip and close this.

[smalyshev]

@mark-vieira should we make some change so that the bot wouldn't just mute the whole test suite?