Re: Announcement: on-demand openQA testing of dist-git pull requests

On 2026/07/21 0:29, Adam Williamson wrote:

> On Mon, 2026-07-20 at 17:15 -0500, Cristian Le via devel wrote:
>> And yeah the more I contemplate, the less of a bad idea it seems to me to just wrap it around a tmt test. It is not much different than the current implementation right?
> I still don't understand the idea here, honestly, or the problem it's
> trying to solve. Could someone explain it to me in small words? :D

I hear your offer of small words and counter it with long paragraphs 😅.

Going back to the original question

> I don't want to invent some kind of system for marking PRs as related
> myself

Best central place to do this would be in packit and if we can bring the 
PR-based openQA tests on there we would file it under the "figure out 
how packit can do that bucket". The other issues would be solved 
automatically as well.

On the how can this be ported to packit, there are 2 possible ways to 
tackle this


      Wrap OpenQA tests as a tmt test

This would be the easiest to approach if a bit inefficient. Afaiu this 
is already similar to how the new PR handler works right? I.e. you 
submit a job via `OpenQAScheduler._update_schedule`, which eventually 
submits a job to OpenQA, waits for the job to finish and then reports 
back. This just needs to be replicated from a CLI or a python API


      |Make OpenQA another test executor for packit (same as
      testing-farm currently is)|

This is theoretically more efficient, but it depends on how packit can 
interact with OpenQA. From what I can tell from navigating the 
packit-service code, this would not be too difficult to implement.

-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new