workflows: Increase libvirt e2e test timeout #2040
Merged
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
We've seen a few nightly and PR test runs fail due to e2e timeout. Looking into it our timeout for over a year has been fixed at 50m, but in that time we've added a lot of tests and do extra deployment stages, like trustee. Looking at a recently run around half of the 50m allowance was taking up just setting up the cluster before tests run. Whilst I think it would be good to try and refine/filter the tests we run and improve some of the slowness, in the short term increasing the timeout will help us avoid e2e failures and re-runs. Signed-off-by: stevenhorsman <steven@uk.ibm.com>
mkulke
approved these changes
Sep 16, 2024
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.
We've seen a few nightly and PR test runs fail due to e2e timeout. Looking into it our timeout for over a year has been fixed at 50m, but in that time we've added a lot of tests and do extra deployment stages, like trustee. Looking at a recently run around half of the 50m allowance was taking up just setting up the cluster before tests run. Whilst I think it would be good to try and refine/filter the tests we run and improve some of the slowness, in the short term increasing the timeout will help us avoid e2e failures and re-runs.