From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: jsnow@redhat.com, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system
Date: Tue, 24 Jul 2018 09:44:47 -0500 [thread overview]
Message-ID: <bbb762c9-5b7e-757f-9668-ec794bec6f5a@redhat.com> (raw)
In-Reply-To: <20180724084739.580-1-famz@redhat.com>
On 07/24/2018 03:47 AM, Fam Zheng wrote:
> Something has locked /dev/null on my system (I still don't know what to do with
> the annoying incapability of lslocks, or more precisely /proc/locks, on
> inspecting OFD lock information), and as a result 226 cannot pass due to the
> unexpected image locking error.
>
> Fix the test case by disabling locking, and add a doc text about using test
> images.
>
> Fam Zheng (2):
> docs: Describe using images in writing iotests
> iotests: Don't lock /dev/null in 226
>
Reviewed-by: Eric Blake <eblake@redhat.com>
> docs/devel/testing.rst | 11 +++++++++++
> tests/qemu-iotests/226 | 4 ++--
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-07-24 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 8:47 [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system Fam Zheng
2018-07-24 8:47 ` [Qemu-devel] [PATCH 1/2] docs: Describe using images in writing iotests Fam Zheng
2018-07-24 8:47 ` [Qemu-devel] [PATCH 2/2] iotests: Don't lock /dev/null in 226 Fam Zheng
2018-07-24 14:44 ` Eric Blake [this message]
2018-07-24 18:03 ` [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system John Snow
2018-07-27 9:24 ` Fam Zheng
2018-07-27 10:04 ` Kevin Wolf
2018-07-27 12:17 ` Fam Zheng
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=bbb762c9-5b7e-757f-9668-ec794bec6f5a@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.