[8.x] functionaltests: increase timeout and print error logs (backport #15305) #15323
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.
Motivation/summary
We observed some failures in the
functionaltests
pipeline due to:This PR increases the timeout to 30 minutes (from emphirical evidence test runs where lasting around the 16 minutes mark) to overcome future timeouts.
To handle unexpected Elasticsearch error this PR adds a print of the retrieved document sources. This will help troubleshoot errors and act appropriately (errors may not necessarily be due to APM upgrade or related to the test being run).
Checklist
How to test these changes
https://github.com/elastic/apm-server/actions/runs/12892898046
Related issues
#14100
This is an automatic backport of pull request #15305 done by [Mergify](https://mergify.com).