From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41273) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWUOQ-0001GF-Rw for qemu-devel@nongnu.org; Mon, 31 Aug 2015 15:05:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWUOP-0000hF-UL for qemu-devel@nongnu.org; Mon, 31 Aug 2015 15:05:22 -0400 From: Max Reitz Date: Mon, 31 Aug 2015 21:05:11 +0200 Message-Id: <1441047913-30596-1-git-send-email-mreitz@redhat.com> Subject: [Qemu-devel] [PATCH 0/2] iotests: Emit signal-kill messages List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-block@nongnu.org Cc: Kevin Wolf , qemu-devel@nongnu.org, Max Reitz 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. Max Reitz (2): iotests: Do not suppress segfaults in bash tests iotests: Warn if python subprocess is killed tests/qemu-iotests/039 | 19 ++++++------------- tests/qemu-iotests/039.out | 6 +++--- tests/qemu-iotests/061 | 6 ++++-- tests/qemu-iotests/061.out | 2 ++ tests/qemu-iotests/check | 8 ++++---- tests/qemu-iotests/common.config | 34 ++++++++++++++++++++++++++++++---- tests/qemu-iotests/common.rc | 12 +++++++++++- tests/qemu-iotests/iotests.py | 32 ++++++++++++++++++++++++-------- 8 files changed, 84 insertions(+), 35 deletions(-) -- 2.5.0