From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55666) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZXWOQ-0001Qw-BX for qemu-devel@nongnu.org; Thu, 03 Sep 2015 11:25:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZXWOM-00083Q-Dr for qemu-devel@nongnu.org; Thu, 03 Sep 2015 11:25:38 -0400 Date: Thu, 3 Sep 2015 17:25:26 +0200 From: Kevin Wolf Message-ID: <20150903152526.GD8138@noname.redhat.com> References: <1441219948-13242-1-git-send-email-mreitz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1441219948-13242-1-git-send-email-mreitz@redhat.com> Subject: Re: [Qemu-devel] [PATCH v2 0/4] iotests: Emit signal-kill messages List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: Jeff Cody , qemu-devel@nongnu.org, qemu-block@nongnu.org Am 02.09.2015 um 20:52 hat Max Reitz geschrieben: > Currently, if a qemu-related command (qemu, qemu-io, qemu-img, qemu-nbd) > is invoked in an iotest, receives a signal and is subsequently killed > (e.g. a segmentation fault), this is not logged in the test output. The > first patch in this series makes the bash tests no longer suppress that > line, and the second patch adds a similar notification for the python > tests. > > Patch 3 tries to fix some handling of spaces in command filenames, and > apparently actually succeeds in doing so (all Python tests work, most > bash tests work; if they fail, it's the test's fault). However, it does > not fix handling of spaces in arguments: This is because we probably > don't have to worry about that anyway, and because it would be pretty > difficult to fix. Thanks, applied to the block branch. Kevin