[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] iotests: don't test qcow2.py inside 291
From: |
Eric Blake |
Subject: |
Re: [PATCH] iotests: don't test qcow2.py inside 291 |
Date: |
Thu, 18 Jun 2020 10:54:05 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 |
On 6/18/20 10:40 AM, Vladimir Sementsov-Ogievskiy wrote:
820c6bee534ec3b added testing of qcow2.;y into 291, and it breaks 291
s/;y/py/
with external data file. Actually, 291 is bad place for qcow2.py
testing, better add a separate test.
Now, drop qcow2.py testing from 291 to fix regression.
s/Now/For now/
s/fix/fix the/
Fixes: 820c6bee534ec3b
Reported-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
---
tests/qemu-iotests/291 | 4 ----
tests/qemu-iotests/291.out | 33 ---------------------------------
2 files changed, 37 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
I can take this through my bitmaps tree, although I'm also fine if Max
takes it through the iotests tree. Either way, it will get in.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org