From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] iotests: Skip test for ENOMEM error
Date: Thu, 1 Mar 2018 14:15:20 -0600 [thread overview]
Message-ID: <588236fe-472d-a028-a448-e2a6aba84697@redhat.com> (raw)
In-Reply-To: <20180301011413.11531-1-famz@redhat.com>
On 02/28/2018 07:14 PM, Fam Zheng wrote:
> The AFL image is to exercise the code validating image size, which
> doesn't work on 32 bit or when out of memory (there is a large
> allocation before the interesting point). So check that and skip the
> test, instead of faking the result.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> tests/qemu-iotests/059 | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
>
> diff --git a/tests/qemu-iotests/059 b/tests/qemu-iotests/059
> index 40f89eae18..530bbbe6ce 100755
> --- a/tests/qemu-iotests/059
> +++ b/tests/qemu-iotests/059
> @@ -152,9 +152,8 @@ done
> echo
> echo "=== Testing afl image with a very large capacity ==="
> _use_sample_img afl9.vmdk.bz2
> -# The sed makes this test pass on machines with little RAM
> -# (and also with 32 bit builds)
> -_img_info | sed -e 's/Cannot allocate memory/Invalid argument/'
> +_img_info | grep -q 'Cannot allocate memory' && _notrun "Insufficent memory, skipped test"
> +_img_info
> _cleanup_test_img
>
> # success, all done
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-03-01 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 1:14 [Qemu-devel] [PATCH] iotests: Skip test for ENOMEM error Fam Zheng
2018-03-01 20:15 ` Eric Blake [this message]
2018-03-05 17:06 ` 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=588236fe-472d-a028-a448-e2a6aba84697@redhat.com \
--to=eblake@redhat.com \
--cc=famz@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).