From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Juan Quintela" <quintela@redhat.com>,
qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Peter Xu" <peterx@redhat.com>
Subject: Re: [PATCH] tests/qtest/migration-test: Only wait for serial output where migration succeeds
Date: Thu, 18 Aug 2022 18:07:18 +0100 [thread overview]
Message-ID: <Yv5xxvrpbd0tXUCi@work-vm> (raw)
In-Reply-To: <20220818162144.227542-1-thuth@redhat.com>
* Thomas Huth (thuth@redhat.com) wrote:
> Waiting for the serial output can take a couple of seconds - and since
> we're doing a lot of migration tests, this time easily sums up to
> multiple minutes. But if a test is supposed to fail, it does not make
> much sense to wait for the source to be in the right state first, so
> we can skip the waiting here. This way we can speed up all tests where
> the migration is supposed to fail. In the gitlab-CI gprov-gcov test,
> each of the migration-tests now run two minutes faster!
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/qtest/migration-test.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
> index 520a5f917c..7be321b62d 100644
> --- a/tests/qtest/migration-test.c
> +++ b/tests/qtest/migration-test.c
> @@ -1307,7 +1307,9 @@ static void test_precopy_common(MigrateCommon *args)
> }
>
> /* Wait for the first serial output from the source */
> - wait_for_serial("src_serial");
> + if (args->result == MIG_TEST_SUCCEED) {
> + wait_for_serial("src_serial");
> + }
I think this is OK, albeit only because all of the current fail-tests
are ones where the connection fails; we're not relying on the behaviour
of the emulator at all. I wonder if it's worth going further and
running the source qemu's with -S (which may or not fail in other ways).
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
> if (!args->connect_uri) {
> g_autofree char *local_connect_uri =
> --
> 2.31.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2022-08-18 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 16:21 [PATCH] tests/qtest/migration-test: Only wait for serial output where migration succeeds Thomas Huth
2022-08-18 17:07 ` Dr. David Alan Gilbert [this message]
2022-08-22 10:56 ` Daniel P. Berrangé
2022-08-22 10:55 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yv5xxvrpbd0tXUCi@work-vm \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.