From: Luiz Capitulino <lcapitulino@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qmp: Check for returned data from __json_read in get_events
Date: Fri, 28 Feb 2014 13:36:19 -0500 [thread overview]
Message-ID: <20140228133619.2acad465@redhat.com> (raw)
In-Reply-To: <1393220701-27172-1-git-send-email-famz@redhat.com>
On Mon, 24 Feb 2014 13:45:01 +0800
Fam Zheng <famz@redhat.com> wrote:
> When QEMU process aborts and socket is closed, qmp client will not
> detect it. When this happens, some qemu-iotests scripts will enter an
> endless loop waiting for qmp events.
>
> It's better we raise an exception in qmp.py to catch this and make the
> test script stop.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
Applied to the qmp branch, thanks.
> ---
> scripts/qmp/qmp.py | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/qmp/qmp.py b/scripts/qmp/qmp.py
> index 5c97175..20b6ec7 100644
> --- a/scripts/qmp/qmp.py
> +++ b/scripts/qmp/qmp.py
> @@ -171,7 +171,12 @@ class QEMUMonitorProtocol:
> pass
> self.__sock.setblocking(1)
> if not self.__events and wait:
> - self.__json_read(only_event=True)
> + ret = self.__json_read(only_event=True)
> + if ret == None:
> + # We are in blocking mode, if don't get anything, something
> + # went wrong
> + raise QMPConnectError("Error while reading from socket")
> +
> return self.__events
>
> def clear_events(self):
prev parent reply other threads:[~2014-02-28 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 5:45 [Qemu-devel] [PATCH] qmp: Check for returned data from __json_read in get_events Fam Zheng
2014-02-24 18:21 ` Stefan Hajnoczi
2014-02-28 18:36 ` Luiz Capitulino [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=20140228133619.2acad465@redhat.com \
--to=lcapitulino@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).