GitHub outage fallout from yesterday / retest-required does not work for some PRs

1 view
Skip to first unread message

Daniel Hiller

unread,
Apr 1, 2026, 4:44:51 AM (8 days ago) Apr 1
to kubevirt-dev
TL;DR: if /retest-required doesn't work, please trigger each status manually by using /test [lane-name] or use /test all

Hey all,

we just noticed that in some cases /retest-required is not working - it's not triggering the test lanes being reported as required as usual.

This is caused by the outage from yesterday, where in some cases no status per lane has been attached to a commit. /retest-required will only work for those status being reported on the commit as pending.

What is shown on the pull request is the required checks of the branch-protection (to which the pull requests being required aka optional: false are being added)
--

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