On Tue, Feb 21, 2023 at 01:27:26PM +0000, Peter Maydell wrote: > The migration-test is annoyingly flaky. Examples: > > https://gitlab.com/qemu-project/qemu/-/jobs/3806090216 > (a FreeBSD job) > 32/648 > ERROR:../tests/qtest/migration-helpers.c:205:wait_for_migration_status: > assertion failed: (g_test_timer_elapsed() < MIGRATION_STATUS_WAIT_TIMEOUT) > ERROR > > on a local macos x86 box: > ▶ 34/621 > ERROR:../../tests/qtest/migration-helpers.c:151:migrate_query_not_failed: > assertion failed: (!g_ > str_equal(status, "failed")) ERROR > 34/621 qemu:qtest+qtest-i386 / qtest-i386/migration-test > ERROR 168.12s killed by signal 6 SIGABRT > ――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― > stderr: > qemu-system-i386: Failed to peek at channel > query-migrate shows failed migration: Unable to write to socket: Broken pipe > ** > ERROR:../../tests/qtest/migration-helpers.c:151:migrate_query_not_failed: > assertion failed: (!g_str_equal(status, "failed")) > > (test program exited with status code -6)
THis particular one looks like a recent regresssion. The 'Failed to peek at' message refers to a patch series that merged last week I believe. Probably not the fault of that series. Rather the test is now exposed to yet another failure scenario. It probably would have failed with a different message before this. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
