tests: increase timeout on testCPUSecurityMitigationsEnable #19613
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
This test barely makes it within the default 10 minutes timeout. From what I see most of the time is spent by waiting for multiple reboots of the machine. Locally this took almost 7 minutes to run so for CI we can bump this timeout to 20 minutes.
|
Meh, lots of new flakes here from 3x affected. The testCryptoPolicies timeouts are harder, as a successful run takes less than 5 mins. So if you are looking for something else, please create a new PR which amplifies that test, and let it run with verbosity, so that we know where exactly it hangs. (Ping me on chat for details) In the meantime, one round of retries, as this is really trivial and separate. |
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.
This test barely makes it within the default 10 minutes timeout. From what I see most of the time is spent by waiting for multiple reboots of the machine.
Locally this took almost 7 minutes to run so for CI we can bump this timeout to 20 minutes.