Skip to content

[Backport release-1.33] Tune OS test timeouts for e2e runs#7834

Open
k0s-bot wants to merge 3 commits into
release-1.33from
backport-7819-to-release-1.33
Open

[Backport release-1.33] Tune OS test timeouts for e2e runs#7834
k0s-bot wants to merge 3 commits into
release-1.33from
backport-7819-to-release-1.33

Conversation

@k0s-bot

@k0s-bot k0s-bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Automated backport to release-1.33, triggered by a label in #7819.
See .

twz123 added 3 commits June 19, 2026 11:11
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>
(cherry picked from commit cccefbf)
(cherry picked from commit 36dc625)
(cherry picked from commit 03fb7f1)
(cherry picked from commit ea24fa5)
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>
(cherry picked from commit 9746895)
(cherry picked from commit a23c8cc)
(cherry picked from commit cca1b47)
(cherry picked from commit 7a535b5)
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>
(cherry picked from commit cfc1ab1)
(cherry picked from commit 255f479)
(cherry picked from commit c3b437b)
(cherry picked from commit c39a6ba)
@k0s-bot k0s-bot requested review from a team as code owners June 19, 2026 11:11
@k0s-bot k0s-bot requested review from jnummelin and kke June 19, 2026 11:11
@twz123 twz123 changed the title [Backport release-1.33] [Backport release-1.34] Tune OS test timeouts for e2e runs [Backport release-1.33] Tune OS test timeouts for e2e runs Jun 19, 2026
@twz123 twz123 added bug Something isn't working area/ci labels Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants