All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Hanna Reitz <hreitz@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, jsnow@redhat.com
Subject: Re: [PATCH v4 19/19] iotests: specify some unsupported_imgopts for python iotests
Date: Thu, 23 Dec 2021 17:44:18 +0300	[thread overview]
Message-ID: <96899f9f-88ee-bea2-0839-a1e3b10222c2@virtuozzo.com> (raw)
In-Reply-To: <d7f70d12-7fe3-ed2f-9959-79a86cf1d4e6@redhat.com>

23.12.2021 15:44, Hanna Reitz wrote:
> On 03.12.21 14:07, Vladimir Sementsov-Ogievskiy wrote:
>> We support IMGOPTS for python iotests now. Still a lot of tests are
>> unprepared to common IMGOPTS that are used with bash iotests. So we
>> should define corresponding unsupported_imgopts.
>>
>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>> ---
>>   tests/qemu-iotests/044                                 | 3 ++-
>>   tests/qemu-iotests/065                                 | 3 ++-
>>   tests/qemu-iotests/163                                 | 3 ++-
>>   tests/qemu-iotests/165                                 | 3 ++-
>>   tests/qemu-iotests/196                                 | 3 ++-
>>   tests/qemu-iotests/242                                 | 3 ++-
>>   tests/qemu-iotests/246                                 | 3 ++-
>>   tests/qemu-iotests/254                                 | 3 ++-
>>   tests/qemu-iotests/260                                 | 4 ++--
>>   tests/qemu-iotests/274                                 | 3 ++-
>>   tests/qemu-iotests/281                                 | 3 ++-
>>   tests/qemu-iotests/303                                 | 3 ++-
>>   tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test | 3 ++-
>>   tests/qemu-iotests/tests/migrate-bitmaps-test          | 3 ++-
>>   tests/qemu-iotests/tests/migrate-during-backup         | 3 ++-
>>   tests/qemu-iotests/tests/remove-bitmap-from-backing    | 3 ++-
>>   16 files changed, 32 insertions(+), 17 deletions(-)
> 
> Few of these tests look like they could be made to support refcount_bits if we filtered qemu-img info output accordingly, but I don’t mind just marking the option as unsupported, so I’m good with your approach.
> 
>> diff --git a/tests/qemu-iotests/044 b/tests/qemu-iotests/044
>> index 714329eb16..a5ee9a7ded 100755
>> --- a/tests/qemu-iotests/044
>> +++ b/tests/qemu-iotests/044
>> @@ -118,4 +118,5 @@ class TestRefcountTableGrowth(iotests.QMPTestCase):
>>   if __name__ == '__main__':
>>       iotests.activate_logging()
>>       iotests.main(supported_fmts=['qcow2'],
>> -                 supported_protocols=['file'])
>> +                 supported_protocols=['file'],
>> +                 unsupported_imgopts=['refcount_bits'])
>> diff --git a/tests/qemu-iotests/065 b/tests/qemu-iotests/065
>> index 4b3c5c6c8c..f7c1b68dad 100755
>> --- a/tests/qemu-iotests/065
>> +++ b/tests/qemu-iotests/065
>> @@ -139,4 +139,5 @@ TestQMP = None
>>   if __name__ == '__main__':
>>       iotests.main(supported_fmts=['qcow2'],
>> -                 supported_protocols=['file'])
>> +                 supported_protocols=['file'],
>> +                 unsupported_imgopts=['refcount_bits'])
>> diff --git a/tests/qemu-iotests/163 b/tests/qemu-iotests/163
>> index dedce8ef43..0b00df519c 100755
>> --- a/tests/qemu-iotests/163
>> +++ b/tests/qemu-iotests/163
>> @@ -169,4 +169,5 @@ ShrinkBaseClass = None
>>   if __name__ == '__main__':
>>       iotests.main(supported_fmts=['raw', 'qcow2'],
>> -                 supported_protocols=['file'])
>> +                 supported_protocols=['file'],
>> +                 unsupported_imgopts=['compat=0.10'])
> 
> Works for my case (I use -o compat=0.10), but compat=v2 is also allowed.
> 
> For cases that don’t support anything but refcount_bits=16, you already disallow specifying any refcount_bits value, even refcount_bits=16 (which would work fine in most cases, I believe). Perhaps we should then also just disallow any compat option instead of compat=0.10 specifically?
> 
> [...]
> 
>> diff --git a/tests/qemu-iotests/tests/migrate-during-backup b/tests/qemu-iotests/tests/migrate-during-backup
>> index 34103229ee..12cc4dde2e 100755
>> --- a/tests/qemu-iotests/tests/migrate-during-backup
>> +++ b/tests/qemu-iotests/tests/migrate-during-backup
>> @@ -94,4 +94,5 @@ class TestMigrateDuringBackup(iotests.QMPTestCase):
>>   if __name__ == '__main__':
>>       iotests.main(supported_fmts=['qcow2'],
>> -                 supported_protocols=['file'])
>> +                 supported_protocols=['file'],
>> +                 unsupported_imgopts=['compat=0.10'])
> 
> It seems to me like this test can handle compat=0.10 just fine, though.
> 

Hmm, right, it works.


-- 
Best regards,
Vladimir


      reply	other threads:[~2021-12-23 14:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 13:07 [PATCH v4 00/19] iotests: support zstd Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 01/19] iotests.py: img_info_log(): rename imgopts argument Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 02/19] iotests.py: qemu_img*("create"): support IMGOPTS='compression_type=zstd' Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 03/19] iotests: drop qemu_img_verbose() helper Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 04/19] iotests.py: rewrite default luks support in qemu_img Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 05/19] iotest 303: explicit compression type Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 06/19] iotest 065: " Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 07/19] iotests.py: filter out successful output of qemu-img create Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 08/19] iotests.py: filter compression type out Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 09/19] iotest 302: use img_info_log() helper Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 10/19] qcow2: simple case support for downgrading of qcow2 images with zstd Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 11/19] iotests/common.rc: introduce _qcow2_dump_header helper Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 12/19] iotests: massive use _qcow2_dump_header Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 13/19] iotest 39: " Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 14/19] iotests: bash tests: filter compression type Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 15/19] iotests 60: more accurate set dirty bit in qcow2 header Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 16/19] iotest 214: explicit compression type Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 17/19] iotests: declare lack of support for compresion_type in IMGOPTS Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 18/19] iotests.py: implement unsupported_imgopts Vladimir Sementsov-Ogievskiy
2021-12-23 12:41   ` Hanna Reitz
2021-12-23 14:44     ` Vladimir Sementsov-Ogievskiy
2021-12-03 13:07 ` [PATCH v4 19/19] iotests: specify some unsupported_imgopts for python iotests Vladimir Sementsov-Ogievskiy
2021-12-23 12:44   ` Hanna Reitz
2021-12-23 14:44     ` Vladimir Sementsov-Ogievskiy [this message]

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=96899f9f-88ee-bea2-0839-a1e3b10222c2@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=hreitz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@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.