|
From: | Eric Blake |
Subject: | Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system |
Date: | Tue, 24 Jul 2018 09:44:47 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 |
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 <address@hidden>
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
[Prev in Thread] | Current Thread | [Next in Thread] |