We are currently facing the problem that the "gcov-gprof" CI jobs in the gitlab-CI are running way too long - which happens since the migration-tests have been enabled there recently.
These patches now speed up the migration tests, so that the CI job should be fine again. This is how it looked like before my modifications: https://gitlab.com/thuth/qemu/-/jobs/2888957948#L46 ... 5/243 qemu:qtest+qtest-aarch64 / qtest-aarch64/migration-test OK 1265.22s 8/243 qemu:qtest+qtest-x86_64 / qtest-x86_64/migration-test OK 1138.82s And this is how it looks like after the patches have been applied: https://gitlab.com/thuth/qemu/-/jobs/2905108018#L48 ... 5/243 qemu:qtest+qtest-aarch64 / qtest-aarch64/migration-test OK 251.14s 8/243 qemu:qtest+qtest-x86_64 / qtest-x86_64/migration-test OK 336.94s That means the CI job is running ca. 30 minutes faster here now! Thomas Huth (4): tests/qtest/migration-test: Only wait for serial output where migration succeeds tests/migration/aarch64: Speed up the aarch64 migration test tests/migration/i386: Speed up the i386 migration test (when using TCG) tests/qtest/migration-test: Remove duplicated test_postcopy from the test plan tests/migration/aarch64/a-b-kernel.h | 10 +++++----- tests/migration/i386/a-b-bootblock.h | 12 ++++++------ tests/qtest/migration-test.c | 5 +++-- tests/migration/aarch64/a-b-kernel.S | 3 +-- tests/migration/i386/a-b-bootblock.S | 1 + 5 files changed, 16 insertions(+), 15 deletions(-) -- 2.31.1