[CI] CcsCommonYamlTestSuiteIT test {p0=search/160_exists_query/Test exists query on mapped geo_point field with no doc values} failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic #10755 / encryption-at-rest
• elasticsearch-pull-request #93703 / part-6
• elasticsearch-pull-request #93431 / part-6

Reproduction Line:

./gradlew ":qa:ccs-common-rest:yamlRestTest" --tests "org.elasticsearch.test.rest.yaml.CcsCommonYamlTestSuiteIT.test {p0=search/160_exists_query/Test exists query on mapped geo_point field with no doc values}" -Dtests.seed=1B3DEA5C5F8B36CF -Dtests.locale=hy-Armn-AM -Dtests.timezone=Africa/Ndjamena -Druntime.java=25

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.Exception: Test abandoned because suite timeout was reached.

Issue Reasons:

• [main] 3 failures in test test {p0=search/160_exists_query/Test exists query on mapped geo_point field with no doc values} (0.7% fail rate in 435 executions)
• [main] 2 failures in step part-6 (1.6% fail rate in 128 executions)
• [main] 2 failures in pipeline elasticsearch-pull-request (1.6% fail rate in 128 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] 3 failures in test test {p0=search/160_exists_query/Test exists query on mapped geo_point field with no doc values} (0.7% fail rate in 435 executions)
• [main] 2 failures in step part-6 (1.6% fail rate in 128 executions)
• [main] 2 failures in pipeline elasticsearch-pull-request (1.6% fail rate in 128 executions)

Build Scans:

• elasticsearch-periodic #10755 / encryption-at-rest
• elasticsearch-pull-request #93703 / part-6
• elasticsearch-pull-request #93431 / part-6

[elasticsearchmachine]

Pinging @elastic/es-search-foundations (Team:Search Foundations)

[cbuescher]

Another one related to #133409, again only three timeouts in one week, two in a particular PR and one in an "encryption-at-rest" build.
https://es-delivery-stats.elastic.dev/app/dashboards#/view/dcec9e60-72ac-11ee-8f39-55975ded9e63?_g=(refreshInterval:(pause:!t,value:60000),time:(from:now-7d%2Fd,to:now))

I currently only see the option of:

• increasing the timeout even more to make these "encryption-at-rest" build happy
• figure out what makes these builds so much slower. Last time I checked I didn't get a clear team owning these builds though, needs more digging and will take longer I think.