On Thu, Jan 28, 2021 at 10:39:16AM +0100, Vít Ondruch wrote: > 2) I would really love you to stop using VMs for your build/testing. With > exception of Kernel and Kernel related issues, the argument of "mock being > slow" can't stand. Every VM will be more resources hungry then mock, slowing > every your task. The point of having a VM is to have a live installed OS so you can install and test runtime functionality the builds after they have completed. Mock is not generally a substitute for this because mock environment is not a running OS, it is just a chroot, so only a subset of packages can be viably tested inside mock. > 3) The argument of mock being slow can't stand, because in one of my > examples I posted elsewhere in this thread, I picked up the simplest package > I could and the build took 7 seconds. This is certainly not slow, in this > time you can't even switch to your email client to check your emails. I don't see numbers anything like that good with 'fedpkg mockbuild', Taking my "libvirt-glib" package as a test 'fedpkg local' - 30 seconds 'fedpkg mockbuild' - 60 seconds (warm cache) 'fedpkg mockbuild' - 5 minutes (no cache) and that's on my fast laptop with fast SSD. On my machine development server which is a few years older 'fedpkg local' - 48 seconds 'fedpkg mockbuild' - 2 minutes 30 seconds (warm cache) 'fedpkg mockbuild' - 6 minutes 50 seconds (no cache) In this case /home is on SSD, and / is HDD. Thus mock ends up using the slower storage since it isn't using /home. 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
