From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/2] iotests: Warn if python subprocess is killed
Date: Tue, 8 Sep 2015 17:37:04 -0400 [thread overview]
Message-ID: <55EF5500.4080904@redhat.com> (raw)
In-Reply-To: <55EF5347.8020503@redhat.com>
On 09/08/2015 05:29 PM, Max Reitz wrote:
> On 08.09.2015 23:25, John Snow wrote:
>>
>>
>> On 08/31/2015 03:05 PM, Max Reitz wrote:
>>> Currently, if a subprocess of a python test (i.e. qemu-io,
>>> qemu-img, or qemu) receives a signal and is subsequently
>>> aborted, this is not logged.
>>>
>>> This patch makes python tests always check the exit code of
>>> these subprocesses, and emit a message if they have been
>>> killed.
>>>
>>> Signed-off-by: Max Reitz <mreitz@redhat.com> ---
>>> tests/qemu-iotests/iotests.py | 26 +++++++++++++++++++++----- 1
>>> file changed, 21 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/tests/qemu-iotests/iotests.py
>>> b/tests/qemu-iotests/iotests.py index 927c74a..d082597 100644
>>> --- a/tests/qemu-iotests/iotests.py +++
>>> b/tests/qemu-iotests/iotests.py @@ -49,20 +49,34 @@
>>> socket_scm_helper = os.environ.get('SOCKET_SCM_HELPER',
>>> 'socket_scm_helper') def qemu_img(*args): '''Run qemu-img and
>>> return the exit code''' devnull = open('/dev/null', 'r+') -
>>> return subprocess.call(qemu_img_args + list(args),
>>> stdin=devnull, stdout=devnull) + exitcode =
>>> subprocess.call(qemu_img_args + list(args), stdin=devnull,
>>> stdout=devnull) + if exitcode < 0: +
>>> sys.stderr.write('qemu-img received signal %i: %s\n' %
>>> (-exitcode, ' '.join(qemu_img_args + list(args)))) + return
>>> exitcode
>>>
>>
>> Why tack on the arguments after the retcode for the print? The
>> format makes it look like it should be a description for the
>> signal received.
>
> qemu_img_args contains the qemu-img filename as well, so it should
> be obvious that that is the command line.
>
> For the "why": I hope it will make debugging easier by providing
> the exact command line so you can reproduce the problem outside of
> the test.
>
> Max
>
Sorry for being captain bikeshed: can this be something like:
"%s received signal %i; args: %s"
to avoid the string looking like it was meant to answer the question
of what the signal was?
I won't insist on it, though:
Reviewed-by: John Snow <jsnow@redhat.com>
>>
>>> def qemu_img_verbose(*args): '''Run qemu-img without
>>> suppressing its output and return the exit code''' - return
>>> subprocess.call(qemu_img_args + list(args)) + exitcode =
>>> subprocess.call(qemu_img_args + list(args)) + if exitcode <
>>> 0: + sys.stderr.write('qemu-img received signal %i:
>>> %s\n' % (-exitcode, ' '.join(qemu_img_args + list(args)))) +
>>> return exitcode
>>>
>>> def qemu_img_pipe(*args): '''Run qemu-img and return its
>>> output''' - return subprocess.Popen(qemu_img_args +
>>> list(args), stdout=subprocess.PIPE).communicate()[0] + subp
>>> = subprocess.Popen(qemu_img_args + list(args),
>>> stdout=subprocess.PIPE) + exitcode = subp.wait() + if
>>> exitcode < 0: + sys.stderr.write('qemu-img received
>>> signal %i: %s\n' % (-exitcode, ' '.join(qemu_img_args +
>>> list(args)))) + return subp.communicate()[0]
>>>
>>> def qemu_io(*args): '''Run qemu-io and return the stdout
>>> data''' args = qemu_io_args + list(args) - return
>>> subprocess.Popen(args,
>>> stdout=subprocess.PIPE).communicate()[0] + subp =
>>> subprocess.Popen(args, stdout=subprocess.PIPE) + exitcode =
>>> subp.wait() + if exitcode < 0: +
>>> sys.stderr.write('qemu-io received signal %i: %s\n' %
>>> (-exitcode, ' '.join(args))) + return subp.communicate()[0]
>>>
>>> def compare_images(img1, img2): '''Return True if two image
>>> files are identical''' @@ -197,7 +211,9 @@ class VM(object):
>>> '''Terminate the VM and clean up''' if not self._popen is
>>> None: self._qmp.cmd('quit') - self._popen.wait() +
>>> exitcode = self._popen.wait() + if exitcode < 0: +
>>> sys.stderr.write('qemu received signal %i: %s\n' % (-exitcode,
>>> ' '.join(self._args))) os.remove(self._monitor_path)
>>> os.remove(self._qtest_path) os.remove(self._qemu_log_path)
>>>
>
>
next prev parent reply other threads:[~2015-09-08 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 19:05 [Qemu-devel] [PATCH 0/2] iotests: Emit signal-kill messages Max Reitz
2015-08-31 19:05 ` [Qemu-devel] [PATCH 1/2] iotests: Do not suppress segfaults in bash tests Max Reitz
2015-08-31 22:55 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2015-09-02 15:09 ` Max Reitz
2015-09-02 15:30 ` Jeff Cody
2015-10-29 14:57 ` [Qemu-devel] " Kevin Wolf
2015-10-29 18:05 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2015-08-31 19:05 ` [Qemu-devel] [PATCH 2/2] iotests: Warn if python subprocess is killed Max Reitz
2015-09-08 21:25 ` [Qemu-devel] [Qemu-block] " John Snow
2015-09-08 21:29 ` Max Reitz
2015-09-08 21:37 ` John Snow [this message]
2015-09-08 21:38 ` Max Reitz
2015-09-08 21:42 ` John Snow
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=55EF5500.4080904@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).