From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: huangy81@chinatelecom.cn, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] tests/migration: fix unix socket migration
Date: Fri, 9 Jul 2021 18:25:53 +0100 [thread overview]
Message-ID: <YOiGoSJcdkYnAYZE@redhat.com> (raw)
In-Reply-To: <f9a92156-8491-4494-c325-4153abc474ea@redhat.com>
On Wed, Jul 07, 2021 at 10:28:10AM +0200, Philippe Mathieu-Daudé wrote:
> On 3/9/21 5:00 PM, huangy81@chinatelecom.cn wrote:
> > From: Hyman <huangy81@chinatelecom.cn>
> >
> > The test aborts and error message as the following be throwed:
> > "No such file or directory: '/var/tmp/qemu-migrate-{pid}.migrate",
> > when the unix socket migration test nearly done. The reason is
> > qemu removes the unix socket file after migration before
> > guestperf.py script do it. So pre-check if the socket file exists
> > when removing it to prevent the guestperf program from aborting.
> >
>
> Maintainer could amend:
>
> See also commit f9cc00346d3 ("tests/migration: fix unix socket batch
> migration").
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
I'll send this one in a pull req i'm preparing.
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 :|
prev parent reply other threads:[~2021-07-09 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 16:00 [PATCH] tests/migration: fix unix socket migration huangy81
2021-03-09 16:55 ` Philippe Mathieu-Daudé
2021-04-21 1:16 ` Hyman Huang
2021-04-28 17:26 ` Wainer dos Santos Moschetta
2021-06-25 16:33 ` Hyman
2021-07-07 7:31 ` Hyman Huang
2021-03-09 18:56 ` Wainer dos Santos Moschetta
2021-07-07 8:28 ` Philippe Mathieu-Daudé
2021-07-09 17:25 ` Daniel P. Berrangé [this message]
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=YOiGoSJcdkYnAYZE@redhat.com \
--to=berrange@redhat.com \
--cc=huangy81@chinatelecom.cn \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.