+Alex & Paolo On 12/20/21 07:52, Thomas Huth wrote: > On 18/12/2021 17.33, Philippe Mathieu-Daudé wrote: >> Hi, >> >> On 12/15/21 08:33, Thomas Huth wrote: >> >>> ---------------------------------------------------------------- >>> * Add virtio-net failover test >>> * Make qtests a little bit more flexible with regards to reduced configs >>> * Move libssh setup from configure to meson.build >>> * Run device-crash-test in CI >>> * Add jobs for NetBSD and OpenBSD to the CI >>> * Test compilation with MSYS2 in the gitlab-ci, too >>> * Add new virtio-iommu test >>> >>> ---------------------------------------------------------------- >> >>> Laurent Vivier (4): >>> qtest/libqos: add a function to initialize secondary PCI buses >>> tests/qtest: add some tests for virtio-net failover >>> tests/libqtest: add some virtio-net failover migration >>> cancelling tests >>> tests/libqtest: add a migration test with two couples of >>> failover devices >> >> On my ASan build directory I'm sometime getting: >> >> Running test qtest-i386/virtio-net-failover >> (process:1558675): GLib-CRITICAL **: 16:19:12.556: g_rand_int: assertion >> 'rand != NULL' failed > > Weird, since the test is not using that function?
Well it calls g_test_rand_int(), which calls it: https://github.com/GNOME/glib/blob/main/glib/gtestutils.c#L1800 > Could you get a > backtrace? I'd like to, but for some reason when using ASan I don't get much (and it only happens with ASan) so I suppose it is something specific to ASan + rand.
