Skip to content

[Backport release-1.35] Tune OS test timeouts for e2e runs#7808

Merged
twz123 merged 3 commits into
release-1.35from
backport-7806-to-release-1.35
Jun 18, 2026
Merged

[Backport release-1.35] Tune OS test timeouts for e2e runs#7808
twz123 merged 3 commits into
release-1.35from
backport-7806-to-release-1.35

Conversation

@k0s-bot

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

Copy link
Copy Markdown
Contributor

Automated backport to release-1.35, triggered by a label in #7806.
See .

twz123 added 3 commits June 16, 2026 12:44
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)
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)
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)
@k0s-bot k0s-bot requested review from a team as code owners June 16, 2026 12:44
@k0s-bot k0s-bot requested review from kke and makhov June 16, 2026 12:44
@twz123 twz123 changed the title [Backport release-1.35] [Backport release-1.36] Tune OS test timeouts for e2e runs [Backport release-1.35] Tune OS test timeouts for e2e runs Jun 16, 2026
@twz123 twz123 added bug Something isn't working area/ci backport/release-1.34 PR that needs to be backported/cherrypicked to the release-1.34 branch labels Jun 16, 2026
@twz123 twz123 enabled auto-merge June 16, 2026 13:12
@twz123 twz123 merged commit e80e96c into release-1.35 Jun 18, 2026
11 checks passed
@twz123 twz123 deleted the backport-7806-to-release-1.35 branch June 18, 2026 10:27
@k0s-bot

k0s-bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor Author

Successfully created backport PR for release-1.34:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci backport/release-1.34 PR that needs to be backported/cherrypicked to the release-1.34 branch bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants