From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, kwolf@redhat.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 for-2.10 1/1] qemu-iotests: _cleanup_qemu must be called on exit
Date: Tue, 18 Apr 2017 14:39:12 -0500 [thread overview]
Message-ID: <c0a0816b-9ff9-a285-dbe1-c5b4f78e6ee4@redhat.com> (raw)
In-Reply-To: <20170418193129.GJ5704@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On 04/18/2017 02:31 PM, Jeff Cody wrote:
> On Tue, Apr 18, 2017 at 01:44:43PM -0500, Eric Blake wrote:
>> On 04/18/2017 12:45 PM, Jeff Cody wrote:
>>> For the tests that use the common.qemu functions for running a QEMU
>>> process, _cleanup_qemu must be called in the exit function.
>>>
>>> If it is not, if the qemu process aborts, then not all of the droppings
>>> are cleaned up (e.g. pidfile, fifos).
>>>
>>
>> Looks like you missed (at least?) 063
>>
>
> I did miss 156. But unless I am missing something, 063 does not use
> common.qemu...
Good point. 063 does litter, even on success, however:
$ rm -rf scratch/
$ ./check -raw 063
...
$ ls scratch/
t.raw.raw1
One idea presented in an earlier thread was that common.rc should create
a subdirectory per test (rather than all tests sharing scratch/), and
then common.rc itself install the cleanup hook that wipes out the entire
subdirectory (or maybe even add a command-line option to ./check to
suppress wiping when it is desirable to debug a test failure by seeing
the droppings left behind).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-04-18 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 17:45 [Qemu-devel] [PATCH v2 for-2.10 1/1] qemu-iotests: _cleanup_qemu must be called on exit Jeff Cody
2017-04-18 18:44 ` Eric Blake
2017-04-18 19:31 ` Jeff Cody
2017-04-18 19:39 ` Eric Blake [this message]
2017-04-18 19:42 ` Jeff Cody
2017-04-19 10:36 ` Fam Zheng
2017-04-19 12:13 ` Max Reitz
2017-04-19 12:36 ` Jeff Cody
2017-04-19 12:45 ` Max Reitz
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=c0a0816b-9ff9-a285-dbe1-c5b4f78e6ee4@redhat.com \
--to=eblake@redhat.com \
--cc=jcody@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).