DocsClientYamlTestSuiteIT times out

[danielmitterdorfer]

Note: We had raised such an issue earlier already (#49753) but I felt a new issue is warranted

While we did not see any timeouts for a while they have come back in recent months so I wanted to raise this issue for us to keep track of these. Here is a time series of the last five months (#49753 has been closed on February 5):

Before June 16, timeouts affected Linux workers but after all timeouts happened on Darwin workers (see attached build stats report generated via filtering for test.failed-testcases.summary: "FAILURE DocsClientYamlTestSuiteIT classMethod" AND test.failed-testcases.message: "java.lang.Exception: Suite timeout exceeded (>= 1800000 msec)." in the last three months).

Build scan: https://gradle-enterprise.elastic.co/s/g3rrfj7scx7ki

Repro line:

./gradlew ':docs:integTestRunner' --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT" \
  -Dtests.seed=A25554FFC677D4B5 \
  -Dtests.security.manager=true \
  -Dtests.locale=en-US \
  -Dtests.timezone=America/Los_Angeles \
  -Druntime.java=11

Reproduces locally?: no

Applicable branches: 7.8, master (see failure history link below for details)

Failure history: timeouts within the last three months

Failure excerpt:

The test suite fails with a timeout:

java.lang.Exception: Suite timeout exceeded (>= 1800000 msec).

[elasticmachine]

Pinging @elastic/es-core-infra (:Core/Infra/Build)

[droberts195]

I think this is #58286. The parallelism was increased on the macOS workers and they cannot cope with it so various suites time out. It's not just the docs tests. Any of the test suites that start up external clusters and run a lot of tests can be affected.

[danielmitterdorfer]

Thanks for the pointer @droberts195! IMHO there is no point having multiple issues for the same underlying cause. I'll close this one then.