On 23.08.2017 14:20, Cornelia Huck wrote: > On Wed, 23 Aug 2017 10:35:43 +0200 > Thomas Huth <th...@redhat.com> wrote: > >> True. And I just learned that you can also already set the SPEED >> variable to either "quick" or "slow" and that we're already using >> g_test_quick() and g_test_slow() in a couple of places to check this. So >> the framework for running quick vs. thorough tests is already there ... >> we just might want to add this to some more tests, I guess... >> >> Question for the maintainers and the test automation folks: Is anybody >> already running "make check SPEED=slow" or is this just rather an >> unheard-of way of running the tests? > > So I tried this on master just for fun, and 'make V=1 SPEED=slow > check-qtest-x86_64' promptly failed for some ivshmem test. > > On x86_86: > TEST: tests/ivshmem-test... (pid=3672) > /x86_64/ivshmem/single: OK > /x86_64/ivshmem/hotplug: OK > /x86_64/ivshmem/memdev: OK > /x86_64/ivshmem/pair: OK > /x86_64/ivshmem/server-msi: ** > ERROR:/home/cohuck/git/qemu/tests/ivshmem-test.c:367:test_ivshmem_server: > assertion failed (ret == 0): (1 == 0) > FAIL > GTester: last random seed: R02Scde8fd6835fdf17450c73e2f74f25007 > (pid=3697) > /x86_64/ivshmem/server-irq: OK > FAIL: tests/ivshmem-test > > On s390x: > TEST: tests/ivshmem-test... (pid=63617) > /x86_64/ivshmem/single: OK > /x86_64/ivshmem/hotplug: OK > /x86_64/ivshmem/memdev: OK > /x86_64/ivshmem/pair: OK > /x86_64/ivshmem/server-msi: > qemu-system-x86_64: -device ivshmem-doorbell,chardev=chr0,vectors=2: server > sent invalid ID message > Broken pipe > FAIL > GTester: last random seed: R02Sda000f7be5ce27b3dfbb03d12f297b69 > (pid=63640) > /x86_64/ivshmem/server-irq: > qemu-system-x86_64: -device ivshmem,size=1M,msi=off,chardev=chr0,vectors=2: > server sent invalid ID message > Broken pipe > FAIL > GTester: last random seed: R02S5a236dbcac35545cc34c0131fbc06162 > (pid=63648) > FAIL: tests/ivshmem-test > > Both machines are on Fedora 26.
The ivshmem test fails for me with SPEED=slow, too (on a x86 RHEL7 machine). Looks like it is definitely broken. Could anybody with some ivshmem knowledge please have a look at this? Thanks, Thomas
