Public bug reported: On building libvirt I got these fails on s390x (all other architectures are fine):
88/162 virdrivermoduletest FAIL 0.04s exit status 1 128/162 storagepoolxml2argvtest FAIL 0.03s exit status 1 129/162 storagepoolxml2xmltest FAIL 0.03s exit status 1 132/162 virstoragetest FAIL 0.03s exit status 1 I checked and it also breaks without my recent changes (regression in release without a libvirt upload) The error messages themselve are not helpful (just no output) LP jammy - works https://launchpad.net/~paelzer/+archive/ubuntu/libvirt-regressed-build-jammy/+build/22402236 LP jammy proposed - fails https://launchpad.net/~paelzer/+archive/ubuntu/libvirt-regressed-build-jammy-proposed/+build/22402343 VM / Container doesn't matter, but the config must be ok For a local repro run: ./debian/rules clean; export DEB_HOST_ARCH=s390x; export DEB_HOST_ARCH_OS=linux; ./debian/rules build The most likely suspect seemed to be glib2 2.68.4 -> 2.70.1 But downgrading that still hit the issue, next I found an actual error message $ VIR_TEST_DEBUG=1 VIR_TEST_RANGE=3 ./debian/build/tests/virdrivermoduletest TEST: virdrivermoduletest 3) Test driver "storage" ... libvirt: error : internal error: Failed to load module '/root/libvirt-7.6.0/debian/build/src/libvirt_storage_backend_gluster.so': /lib/s390x-linux-gnu/libtcmalloc.so.4: cannot allocate memory in static TLS block FAILED The other three tests do not have any useful extended info. But gluster was in that candidate list I was checking. Downgrade Gluster v=9.2-1; apt install libglusterfs-dev=$v libglusterfs0=$v libglusterd0=$v libgfapi0=$v libgfchangelog0=$v libgfrpc0=$v libgfxdr0=$v Working fine with 9.2-1 ** Affects: glusterfs (Ubuntu) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Description changed: - On building libvirt I got these fails: + On building libvirt I got these fails on s390x (all other architectures + are fine): - 88/162 virdrivermoduletest FAIL 0.04s exit status 1 + 88/162 virdrivermoduletest FAIL 0.04s exit status 1 128/162 storagepoolxml2argvtest FAIL 0.03s exit status 1 129/162 storagepoolxml2xmltest FAIL 0.03s exit status 1 132/162 virstoragetest FAIL 0.03s exit status 1 I checked and it also breaks without my recent changes (regression in release without a libvirt upload) The error messages themselve are not helpful (just no output) LP jammy - works - https://launchpad.net/~paelzer/+archive/ubuntu/libvirt-regressed-build-jammy/+build/22402236 + https://launchpad.net/~paelzer/+archive/ubuntu/libvirt-regressed-build-jammy/+build/22402236 LP jammy proposed - fails - https://launchpad.net/~paelzer/+archive/ubuntu/libvirt-regressed-build-jammy-proposed/+build/22402343 + https://launchpad.net/~paelzer/+archive/ubuntu/libvirt-regressed-build-jammy-proposed/+build/22402343 VM / Container doesn't matter, but the config must be ok For a local repro run: ./debian/rules clean; export DEB_HOST_ARCH=s390x; export DEB_HOST_ARCH_OS=linux; ./debian/rules build The most likely suspect seemed to be glib2 2.68.4 -> 2.70.1 But downgrading that still hit the issue, next I found an actual error message - $ VIR_TEST_DEBUG=1 VIR_TEST_RANGE=3 ./debian/build/tests/virdrivermoduletest TEST: virdrivermoduletest - 3) Test driver "storage" ... + 3) Test driver "storage" ... libvirt: error : internal error: Failed to load module '/root/libvirt-7.6.0/debian/build/src/libvirt_storage_backend_gluster.so': /lib/s390x-linux-gnu/libtcmalloc.so.4: cannot allocate memory in static TLS block FAILED - The other three tests do not have any useful extended info. But gluster was in that candidate list I was checking. Downgrade Gluster v=9.2-1; apt install libglusterfs-dev=$v libglusterfs0=$v libglusterd0=$v libgfapi0=$v libgfchangelog0=$v libgfrpc0=$v libgfxdr0=$v Working fine with 9.2-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950777 Title: Glusterfs 1.0 breaks libvirt tests on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
