On Tue, 7 Mar 2023 at 09:53, Peter Maydell <peter.mayd...@linaro.org> wrote: > > On Sat, 4 Mar 2023 at 15:39, Peter Maydell <peter.mayd...@linaro.org> wrote: > > > > On Thu, 2 Mar 2023 at 17:22, Peter Maydell <peter.mayd...@linaro.org> wrote: > > > > > > migration-test has been flaky for a long time, both in CI and > > > otherwise: > > > > > > > > > > In the cases where I've looked at the underlying log, this seems to > > > be in the migration/multifd/tcp/plain/cancel subtest. Disable that > > > specific subtest by default until somebody can track down the > > > underlying cause. Enthusiasts can opt back in by setting > > > QEMU_TEST_FLAKY_TESTS=1 in their environment. > > > > So I'm going to apply this, because hopefully it will improve > > the reliability a bit, but it's clearly not all of the > > issues with migration-test
Here's another one, on the s390x CI runner: https://gitlab.com/qemu-project/qemu/-/jobs/3917587994 31/658 qemu:qtest+qtest-i386 / qtest-i386/migration-test ERROR 34.36s killed by signal 6 SIGABRT >>> QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon >>> QTEST_QEMU_IMG=./qemu-img QTEST_QEMU_BINARY=./qemu-system-i386 >>> G_TEST_DBUS_DAEMON=/home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/tests/dbus-vmstate-daemon.sh >>> MALLOC_PERTURB_=154 >>> /home/gitlab-runner/builds/FLaZkdt1/0/qemu-project/qemu/build/tests/qtest/migration-test >>> --tap -k ――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― stderr: Broken pipe ../tests/qtest/libqtest.c:193: kill_qemu() detected QEMU death from signal 11 (Segmentation fault) (core dumped) TAP parsing error: Too few tests run (expected 40, got 11) (test program exited with status code -6) ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― Do you folks have a concrete proposal for tracking down and fixing the flakiness in this test? If not, we'll have to just disable it entirely, I think. thanks -- PMM