On Sun, 2025-04-20 at 02:47 -0400, Neal Gompa wrote: > > > > OK, sure, I can add it, but I'm a bit confused - what do you mean by > > "they're incredibly helpful to know what has made it through or failed. > > Otherwise I don't know until someone complains."? I'm not quite seeing > > how these emails tell you whether something "made it through" or not? > > Those emails (along with the compose emails) indicate whether any > non-blocking images have failed (such as the aarch64 ISO and the plamo > images) and it's very easy for me to jump straight to the OpenQA test > results if I need to look more deeply at something. I think you're thinking of different emails. You seem to be describing the 'compose check' emails. Those only go to the test-reports@ list ATM because people found the volume kinda overwhelming on devel@ and test@. I *could* send them here too but I'm not sure the whole WG would want them. (I could also just CC them direct to you...) Honestly the 'expected image check' thing is a bit hoary and at some point I was meaning to take it out of fedfind...the failed-composes tracker kinda seems like a better way of doing that job, to me anyway... -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
