On 28/09/2022 12.31, Thomas Huth wrote:
On 27/09/2022 13.05, Bin Meng wrote:
In preparation to adding virtio-9p support on Windows, this series
enables running qtest on Windows, so that we can run the virtio-9p
tests on Windows to make sure it does not break accidently.
Thanks for your patches - I've picked many of them for my pull request that
I sent out earlier today, so you don't have to carry them along anymore once
the PR got merged.
For the patches that are not directly related to tests/ ... could you maybe
ask the corresponding maintainers to pick those up? I'm not sure whether
they should go through my testing branch, too...
Anyway, there seems to be one more issue: The migration test sometimes seems
to be failing on aarch64 with all your patches applied:
87/470 qemu:qtest+qtest-aarch64 / qtest-aarch64/migration-test
ERROR 261.71s killed by signal 6 SIGABRT
>>> MALLOC_PERTURB_=171 QTEST_QEMU_BINARY=./qemu-system-aarch64
QTEST_QEMU_IMG=./qemu-img
G_TEST_DBUS_DAEMON=/home/thuth/devel/qemu/tests/dbus-vmstate-daemon.sh
QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon
/home/thuth/tmp/qemu-build/tests/qtest/migration-test --tap -k
―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stderr:
**
ERROR:../../devel/qemu/tests/qtest/migration-helpers.c:205:wait_for_migration_status:
assertion failed: (g_test_timer_elapsed() < MIGRATION_STATUS_WAIT_TIMEOUT)
../../devel/qemu/tests/qtest/libqtest.c:201: kill_qemu() tried to terminate
QEMU process but encountered exit status 1 (expected 0)
(test program exited with status code -6)
―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
Not sure whether it's really related to your patches or whether it's
something else that has been merged recently, I'm having problems to
reproduce it reliably, but it's definitely something we should keep an eye
on...
Seems like somebody also ran into this issue with a vanilla QEMU:
https://gitlab.com/qemu-project/qemu/-/issues/1230
So it's not related to your patch series.
Thomas