Tune OS test timeouts for e2e runs#7801
Merged
Merged
Conversation
This is useful for the release workflow, where we're only interested in successful runs and a quicker feedback loop. Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
This mostly applies to full conformance test runs that are called from the release workflow. In order to obtain the "Certified Kubernetes" badge, these cannot be run in parallel. They currently take around two hours to complete, close to the Ginkgo test timeout. Funnily enough, the 64-bit ARM VMs are slightly faster than the 64-bit x86_64 VMs, resulting in mostly successful arm64 runs and very unreliable amd64 runs. Moreover, Ginkgo/sonobuoy simply report any overall test timeouts as failures of the pending tests, with no indication that the tests did not even complete. This makes it very difficult to realize that this is a timeout issue rather than a flaky test. For an all-serial workflow step, use the following timeouts: * three hours for Ginkgo, * three and a half hours for Sonobuoy * and four hours for the workflow step. When the serial step follows a parallel step, use tighter timeouts because only the remaining serial tests should run: * thirty minutes for Ginkgo, * forty-five minutes for Sonobuoy, * and one hur for the workflow step. See: 71b3209 ("Use OS tests in release workflow") Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
Keep the format, but instead of writing it into a console group, write it into a step summary. Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
twz123
added
bug
apedriza
approved these changes
Jun 16, 2026
ncopa
approved these changes
Jun 16, 2026
Contributor
|
Successfully created backport PR for |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
This mostly applies to full conformance test runs that are called from the release workflow. In order to obtain the "Certified Kubernetes" badge, these cannot be run in parallel. They currently take around two hours to complete, close to the Ginkgo test timeout. Funnily enough, the 64-bit ARM VMs are slightly faster than the 64-bit x86_64 VMs, resulting in mostly successful arm64 runs and very unreliable amd64 runs. Moreover, Ginkgo/sonobuoy simply report any overall test timeouts as failures of the pending tests, with no indication that the tests did not even complete. This makes it very difficult to realize that this is a timeout issue rather than a flaky test.
For an all-serial workflow step, use the following timeouts:
When the serial step follows a parallel step, use tighter timeouts because only the remaining serial tests should run:
See:
Type of change
How Has This Been Tested?
Checklist