On Thu, Feb 3, 2022 at 7:30 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > > I noticed today that openQA KDE tests for F34 updates were failing. > After a bit of investigation I found the bug had been filed and is in > the process of being fixed: > > https://bugzilla.redhat.com/show_bug.cgi?id=2049560 > > However, ideally, the bug should never have made it to stable. If > openQA tests had run on the initial update, they would have failed and > gating would have prevented the update going stable. > > openQA didn't run on the broken update because the package - qt5- > qtwayland - is not marked as critical path. We only run openQA tests on > critical path updates at present due to capacity limitations. > > I've sent a PR to add qt5-qtwayland to the critpath definition: > https://pagure.io/fedora-comps/pull-request/710 > > but in so doing I noticed the critical-path-kde group is almost empty. > This means when other KDE components are updated, we're not running the > openQA tests and so we won't catch if they break. It would be much > better if someone could come up with a list of critical KDE packages > and populate the group, so that we would properly test and gate updates > with a decent chance of breaking KDE. > > Can someone help produce such a list? Thanks! Thanks for bringing this to our attention, I've converted this into a SIG ticket for us to discuss on our Monday meeting: https://pagure.io/fedora-kde/SIG/issue/171 -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
