[ci] increase timeout for performance pipeline step to 90 min #175044
Conversation
This file contains 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
dmlemeshko
added
release_note:skip
|
/ci |
Ikuni17
approved these changes
Jan 18, 2024
|
#175194 fixes the flakiness in request handling that slows down the run time. But taking into account folks are keep adding new journeys (and today run time is ~50 min) bumping to 90 min is still reasonable. |
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]
History
To update your PR or re-run it, just comment with: |
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this pull request
Feb 15, 2024
…c#175044) ## Summary Recently we have few more journeys added and sometimes overall run time is over 1h and step is aborted because of 60 min timeout. <img width="1088" alt="image" src="https://github.com/elastic/kibana/assets/10977896/8609cea3-12e0-4e3c-83ec-fa441a7d1556"> Increasing timeout to 90 min to avoid re-runs and in the meantime I will start looking into how to optimise & decrease the journeys runtime.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Recently we have few more journeys added and sometimes overall run time is over 1h and step is aborted because of 60 min timeout.
Increasing timeout to 90 min to avoid re-runs and in the meantime I will start looking into how to optimise & decrease the journeys runtime.