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 ? I'm thinking this is not really a libvirt specific problem - any app using Meson is liable to hit the default test suite time limit if running in an emulated chroot, and thus will need to set --timeout-multiplier=10. So perhaps RPM's %meson_test macro should automatically include --timeout-multiplier=10 when running in an emulated world ? Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ 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
