2026-06-03 sig-ci quarantine catch-up - notes

Does anyone want to step in?
briancarey commented: https://github.com/kubevirt/kubevirt/pull/17972#pullrequestreview-4400329227
Dylan to take a look
reference document for upgrading go: https://github.com/kubevirt/kubevirt/blob/main/docs/update-go-version.md
missing in the doc is upgrading of the toolchain, opportunity to add to the doc
1.26 is important precondition because we need to upgrade k8s deps which is built with 1.26, dra people i.e. want this

[nirdothan] let’s discuss the flaking tests lane being required https://redhat-internal.slack.com/archives/C01EX3K1FGE/p1780316410360699

[dhiller] if a test is not fit for the check-tests-for-flakes lane it can receive the no-flake-check decorator
docs say

// NoFlakeCheck decorates tests that are not compatible with the check-tests-for-flakes test lane.
// This should only be used for legitimate purposes, like on tests that have a flake-checker-friendly clone.

solutions

configure the lane to have the infra/reqs to make the test succeed
we also could create specific lanes that have the infrastructure so that those tests can be supported, i.e. specific sig-network flake-check lanes

suggestion: put the decorator in as a band aid in order to signal that the test is not supported yet

to be clear: that decorator should not be put on tests that are really flaky!
when applying the decorator we have to add the reason why it was applied, suggested to have a separate commit with an explaining commit message
we should make `make lint` fail if there’s no separate commit for applying that decorator to a test

structure suggestion: the only change in the commit is the application of the label and a comment, also the commit message as the word `reason` in it

note: similar mechanism enforced by sig-network Ordered decorator
another way would be to mark the PR with a specific label i.e. kind/no-flake-check-added, where the label color would be red, so that it is immediately visible

[dhiller] the optimal outcome would be that as many of the tests running on the “standard” required sig lanes which exist for all three kubernetes versions are also being covered on the check-tests-for-flake lane(s)

this should lead to more overall test stability on the required lanes which should be an achievement that every contributor benefits from

Action items

Daniel Hiller to take this to the mailing list and also community meeting
update/create issues with latest flakes spotted
communication

send meeting notes to kubevirt-dev, bcc sig people for spotted flakes (include meeting changes for upcoming instances)

Kind regards,

Daniel Hiller

He / Him / His

Principal Software Engineer, KubeVirt CI, OpenShift Virtualization

Red Hat

dhi...@redhat.com

Red Hat GmbH, Registered seat: Werner von Siemens Ring 12, D-85630 Grasbrunn, Germany  
Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Avril Crosse O'Flaherty

Reply all

Reply to author

Forward

0 new messages