Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] DocsClientYamlTest regularly fails due to suite timeout #49579

Closed
hendrikmuhs opened this issue Nov 26, 2019 · 5 comments
Closed

[CI] DocsClientYamlTest regularly fails due to suite timeout #49579

hendrikmuhs opened this issue Nov 26, 2019 · 5 comments
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@hendrikmuhs
Copy link

DocsClientYamlTest ran into the suite timeout: https://gradle-enterprise.elastic.co/s/zepwthumo2am2/

Further investigation shows that timeout happened 12 times in the last 7 days, while there is no offending test that took a very long time:

https://gradle-enterprise.elastic.co/s/zepwthumo2am2/tests?test=DocsClientYamlTest

Conclusion: The sum of executed tests got big over time. The timeout is already set to 30 minutes which is quite high, increasing the limit might be a simple fix but maybe it's time to consider other options like splitting the suite into smaller parts.

@hendrikmuhs hendrikmuhs added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI :Docs labels Nov 26, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (:Docs)

@elasticmachine
Copy link
Collaborator

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

@droberts195
Copy link
Contributor

Also worth noting that the docs suite was the one timing out in #48148 (comment)

That was found to be because the docs suite happened to run in parallel with the server suite on the Mac CI workers - see #48148 (comment)

So it may be that on some other combinations of hardware/OS, the scheduling works out that the docs suite runs at the same time as the server suite.

@hendrikmuhs
Copy link
Author

Since 20/01/13 the number of failures increased:

image

@hendrikmuhs
Copy link
Author

Closing this issue in favor of #49753, although its a younger duplicate but the more interesting investigations and discussions happen there.

@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

5 participants