qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
	Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu.py: Fix error message when qemu dies from signal
Date: Mon, 14 Jan 2019 12:04:40 +0100	[thread overview]
Message-ID: <05f29d1e-11f0-62e0-af82-02a989e1c7b7@redhat.com> (raw)
In-Reply-To: <20190111201330.14473-1-eblake@redhat.com>

Hi Eric,

On 1/11/19 9:13 PM, Eric Blake wrote:
> When qemu dies from a signal, the python code gets a negative
> value for exitcode; but signal numbers are positive.  Copy the
> pattern used in qemu-iotests/iotests.py for reporting a positive
> value.
> 
> CC: qemu-trivial@nongnu.org
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>  scripts/qemu.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/qemu.py b/scripts/qemu.py
> index 6e3b0e67719..0a5e02eb56e 100644
> --- a/scripts/qemu.py
> +++ b/scripts/qemu.py
> @@ -351,7 +351,7 @@ class QEMUMachine(object):
>                  command = ' '.join(self._qemu_full_args)
>              else:
>                  command = ''
> -            LOG.warn(msg, exitcode, command)
> +            LOG.warn(msg, -exitcode, command)

What about displaying signal name directly?

import signal

...

            msg = 'qemu received %s: %s'
            ...

            LOG.warn(msg, signal.Signals(-exitcode).name, command)

> 
>          self._launched = False
> 

  reply	other threads:[~2019-01-14 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 20:13 [Qemu-devel] [PATCH] qemu.py: Fix error message when qemu dies from signal Eric Blake
2019-01-14 11:04 ` Philippe Mathieu-Daudé [this message]
2019-01-14 15:36   ` Eric Blake
2019-01-14 16:54     ` Philippe Mathieu-Daudé

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=05f29d1e-11f0-62e0-af82-02a989e1c7b7@redhat.com \
    --to=philmd@redhat.com \
    --cc=crosa@redhat.com \
    --cc=eblake@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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).