From: Juan Quintela <quintela@redhat.com>
To: "Dr. David Alan Gilbert \(git\)" <dgilbert@redhat.com>
Cc: thuth@redhat.com, alex.bennee@linaro.org, qemu-devel@nongnu.org,
peterx@redhat.com
Subject: Re: [PATCH 1/2] tests/migration: Fail on unexpected migration states
Date: Tue, 24 Sep 2019 09:24:32 +0200 [thread overview]
Message-ID: <87r24640nj.fsf@trasno.org> (raw)
In-Reply-To: <20190923131022.15498-2-dgilbert@redhat.com> (David Alan Gilbert's message of "Mon, 23 Sep 2019 14:10:21 +0100")
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> We've got various places where we wait for a migration to enter
> a given state; but if we enter an unexpected state we tend to fail
> in odd ways; add a mechanism for explicitly testing for any state
> which we shouldn't be in.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
> - wait_for_migration_status(from, "postcopy-active");
> + wait_for_migration_status(from, "postcopy-active",
> + (const char * []) { "failed",
> + "completed", NULL });
>
I really preffer not to use that kind of casts.
const char *ungoals[] = { "failed", "completed", NULL };
but as it is you who are doing the patches, I will not complain O:-)
next prev parent reply other threads:[~2019-09-24 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 13:10 [PATCH 0/2] migration test tweeks Dr. David Alan Gilbert (git)
2019-09-23 13:10 ` [PATCH 1/2] tests/migration: Fail on unexpected migration states Dr. David Alan Gilbert (git)
2019-09-23 14:12 ` Cleber Rosa
2019-09-23 16:20 ` Alex Bennée
2019-09-24 7:24 ` Juan Quintela [this message]
2019-09-23 13:10 ` [PATCH 2/2] tests/migration/postcopy: trim migration bandwidth Dr. David Alan Gilbert (git)
2019-09-23 14:14 ` Cleber Rosa
2019-09-23 16:15 ` Alex Bennée
2019-09-24 7:25 ` Juan Quintela
2019-09-23 13:24 ` [PATCH 0/2] migration test tweeks Peter Xu
2019-09-23 13:36 ` Dr. David Alan Gilbert
2019-09-25 10:35 ` Dr. David Alan Gilbert
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=87r24640nj.fsf@trasno.org \
--to=quintela@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--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.