Update timeout on yaml rest tests because they often exceed 1h#142715
Merged
elasticsearchmachine merged 2 commits intoelastic:mainfrom Feb 19, 2026
Merged
Update timeout on yaml rest tests because they often exceed 1h#142715elasticsearchmachine merged 2 commits intoelastic:mainfrom
elasticsearchmachine merged 2 commits intoelastic:mainfrom
Conversation
What is happening now is that whichever test happens to be running when the timeout threshold is crossed will get muted by the CI automation. Once sufficient tests are muted, the timeout is no longer crossed. This means arbitrary tests are muted, not the ones that actually take the longest. Extending the timeout is an interim measure and should be followed up by one or both of these options: * Investigate the slowest tests and decide if they are needed or could be simplified, and try to reduce the total time to within reason * Split the tests into groups that are run on separate test runs, probably in parallel. This costs more in infrastructure, but with less risk of reduce coverage
craigtaverner
added
>test
Collaborator
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
mouhc1ne
approved these changes
Feb 19, 2026
craigtaverner
added
the
auto-merge-without-approval
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is happening now is that whichever test happens to be running when the timeout threshold is crossed will get muted by the CI automation. Once sufficient tests are muted, the timeout is no longer crossed. This means arbitrary tests are muted, not the ones that actually take the longest.
Extending the timeout is an interim measure and should be followed up by one or both of these options:
Fixes #141113
Fixes #141856