On Sat, Jan 30, 2021 at 12:08:18PM -0800, Kevin Fenzi wrote: > On Fri, Jan 29, 2021 at 03:26:18PM +0000, Daniel P. Berrangé wrote: > > When we attempt to build libvirt in Copr, the test suite times out on > > s390 builds. > > > > IIUC, this is because s390 in Copr is using a QEMU emulated system, > > not native hardware, and thus is massively slower to execute. > > > > We don't want to bump up the default test suite timeout unconditonally, > > as that makes it slower to diagnose problems for the common case > > where the build env is not emulated. > > > > Is there a good way to detect that the build is in an emulated copr > > env rather than native. Does Copr / mock set any env variable to > > show that you're emulated ? > > systemd-detect-virt ? > > I've not tested, but I'd expect it to say 'qemu' for the emulated case > and 'kvm' for the vm case? > > But some of our s390x builders are ZVM instances and it says 'zvm' > there. Oh, and for now our 32 bit arm builders return 'qemu' for this as well, even though they are accelerated. This is because they are doing a direct kernel/initramfs boot. If/when we can ever get them on f33, they will be using uefi to boot and would return 'kvm' for this. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
