On Fri, 18 Jan 2019 at 18:26, Philippe Mathieu-Daudé <phi...@redhat.com> wrote: > > On 1/18/19 3:20 PM, Peter Maydell wrote: > > I tried the "raise the timeout" change you suggested on IRC. > > That gave me a pass the first time around but the same failure > > second time I tried it: > > > > MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} > > QTEST_QEMU_BINARY=i386-softmmu/qemu-system-i386 > > QTEST_QEMU_IMG=qemu-img tests/ipmi-bt-test -m=quick -k --tap < > > /dev/null | ./scripts/tap-driver.pl --test-name="ipmi-bt-test" > > ** > > ERROR:tests/ipmi-bt-test.c:319:test_connect: assertion failed: (rv == 1) > > ERROR - too few tests run (expected 4, got 0) > > [1] Abort trap (core dumped) MALLOC_PERTURB_=... | > > Done(1) ./scripts/tap-dr... > > /var/tmp/qemu-test.TATvqX/tests/Makefile.include:856: recipe for > > target 'check-qtest-i386' failed > > I guess I finally figured it out, the test binds IPv4 and on the NetBSD > VM, 'localhost' resolves as IPv6 so the guest can't connect to the test.
This theory doesn't explain why the test sometimes passes and sometimes fails, though... thanks -- PMM