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.
Summary
Closes #176754
Closes #176858
Fleet serverless API integration tests tests have already experienced flakiness due to slowness as they expect a preconfigured Fleet Server host and Elasticsearch output to exist. #176808 added retry logic in the tests, which improved flakiness a lot.
However, it seems we are still experiencing failure due to Saved Object not found errors. This indicates that the test setup with retrying is not fully working as intended: if the default fleet server host or output was not found during setup, the failure should be one of:
This PR increases the timeout of the setup retry and renames the error message thrown by Fleet backend when the SO is not found.
Flaky Test Runner builds