From: Juan Quintela <quintela@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
qemu-devel@nongnu.org, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] tests/migration: Add test for migration to bad destination
Date: Tue, 20 Feb 2018 14:26:26 +0100 [thread overview]
Message-ID: <874lmbx059.fsf@secure.laptop> (raw)
In-Reply-To: <040b3661-52e8-bf66-3751-58e443d03e4d@redhat.com> (Thomas Huth's message of "Tue, 20 Feb 2018 12:56:49 +0100")
Thomas Huth <thuth@redhat.com> wrote:
> On 12.02.2018 17:03, Dr. David Alan Gilbert (git) wrote:
>> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>>
>> Check the source survives.
>>
>> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>> ---
>> tests/migration-test.c | 65 ++++++++++++++++++++++++++++++++++++++------------
>> 1 file changed, 50 insertions(+), 15 deletions(-)
> [...]
>> @@ -615,6 +649,7 @@ int main(int argc, char **argv)
>>
>> qtest_add_func("/migration/postcopy/unix", test_migrate);
>> qtest_add_func("/migration/deprecated", test_deprecated);
>> + qtest_add_func("/migration/bad_dest", test_baddest);
>
> While running "make check", I now see some "Failed to connect socket:
> Connection refused" messages popping up, which is a little bit
> confusing. Would it be possible to silence these messages somehow?
I will take a look at that. I haven't looked where they came from.
Thanks.
Later, Juan.
next prev parent reply other threads:[~2018-02-20 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 16:03 [Qemu-devel] [PATCH 0/2] migration: Fix early failure crash Dr. David Alan Gilbert (git)
2018-02-12 16:03 ` [Qemu-devel] [PATCH 1/2] migration: Fix early failure cleanup Dr. David Alan Gilbert (git)
2018-02-12 16:03 ` [Qemu-devel] [PATCH 2/2] tests/migration: Add test for migration to bad destination Dr. David Alan Gilbert (git)
2018-02-20 11:56 ` Thomas Huth
2018-02-20 13:26 ` Juan Quintela [this message]
2018-02-13 3:56 ` [Qemu-devel] [PATCH 0/2] migration: Fix early failure crash Peter Xu
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=874lmbx059.fsf@secure.laptop \
--to=quintela@redhat.com \
--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.