In the libvirt-jenkins-ci repo, which contains the configuration for the CI environment used by libvirt and related project, in the virt-manager specific configuration we've had this comment for a while: # libxml2's Python 3 bindings don't work properly on FreeBSD, # so skip the test suite there for the time being. See # https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224902 and, accordingly, we haven't been running the test suite on FreeBSD. The bug in question seems to have been fixed in the meantime, so I figured I'd give it another go. Now the test suite no longer fails immediately: what happens instead is that it works its way through a number of tests, and then just hangs there. I tried iteratively commenting out the test where it was hanging, run the test suite again, and repeat the process, but that turned out to take way too long so at some point I just gave up :) Also the various culprits seemed to be mostly unrelated and I even had to go back earlier in the file a few times, so it was probably not a good approach to begin with. I have no idea how to debug this thing. Can an actual virt-manager developer jump in? I'll gladly provide guidance on how to set up a suitable FreeBSD environment - thanks to the libvirt-jenkins-ci project mentioned above, it's a mostly automated process and shouldn't take too much time. -- Andrea Bolognani / Red Hat / Virtualization _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
