On Tue, 25 Nov 2014 11:09:35 +0100 Max Reitz <mre...@redhat.com> wrote:
> Test 039 used to fail because qemu-io -c abort may generate core dumps > even with ulimit -c 0 (and the output then contains "(core dumped)"). > Fix this by adding an option to the "abort" command which allows > specifying a signal number to raise(). Using SIGKILL for example does > not result in a core dump, but it still badly crashes qemu-io (as > desired). > > I am sending this series because we need all tests to work before adding > the check-block target to "make check" (which we will hopefully do > soon). > > > Max Reitz (3): > qemu-io: Let -c abort raise any signal > iotests: Filter for "Killed" in qemu-io output > iotests: Fix test 039 > > qemu-io-cmds.c | 59 > ++++++++++++++++++++++++++++++++++++++-- > tests/qemu-iotests/039 | 12 ++++---- > tests/qemu-iotests/039.out | 6 ++-- > tests/qemu-iotests/common.filter | 2 +- > 4 files changed, 67 insertions(+), 12 deletions(-) > Hi Max, thanks a lot for picking this up to make our poor circumvention obsolete. Michael
