Is packit suitable for tests (kdump tests) that need to start a VM via QEMU and then check the console output?

[Coiby Xu]

Hi,

I'm adding some kdump tests to dracut to prevent dracut's change from
breaking kexec-tools [1]. One suggestion is to make use of packit. The 
kdump tests are different from other tests because we need to reboot 
into the second kernel (a dump-capture kernel) to dump the system 
kernel's memory locally fs or to a remote fs (e.g. an nfs fs). Take the 
nfs-kdump test [2] as an example, here are what this test does,
  1. Build the rpms for dracut and kexec-tools
  2. Download the Fedora 33 Cloud Base Image
  3. Start NFS server in a VM
  4. For the kdump tests done as an NFS client,
    - Install the rpms onto another copy of Fedora 33 Cloud Base Image
    - Start another VM and trigger sysrq to boot into the dump-capture
      kernel to do vmcore dump
    - Check the console output to see if vmcore dump is successful

I'm not sure packit is suitable for these kdump tests. For example, I
need to get the path of the rpm built automatically by packit so the
package can be installed onto the VM image but nowhere can I find
anything related to that in packit's docs [3] or [4]. 

[1] https://github.com/dracutdevs/dracut/pull/1163
[2]
https://src.fedoraproject.org/rpms/kexec-tools/blob/f34/f/tests/scripts/t...
[3] https://packit.dev/docs/testing-farm/
[4] https://docs.fedoraproject.org/en-US/ci/

-- 
Best regards,
Coiby