[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH v4 5/7] iotests: Test driver whitelisting in 093
|
From: |
Max Reitz |
|
Subject: |
Re: [Qemu-block] [PATCH v4 5/7] iotests: Test driver whitelisting in 093 |
|
Date: |
Wed, 18 Sep 2019 08:29:01 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
On 17.09.19 16:25, Andrey Shinkevich wrote:
>
>
> On 17/09/2019 12:20, Max Reitz wrote:
>> null-aio may not be whitelisted. Skip all test cases that require it.
>>
>> (And skip the whole test if null-co is not whitelisted.)
> This solution has been persisting since v1. Nevertheless, I am still not
> clear why not to run the test if the null-aio is the only whitelisted
> driver? Will the null-aio be supported in future?
I don’t see a reason why we’d remove it. But chances are, if any of the
null* drivers is whitelisted, it’ll be null-co (because we barely use
the AIO block driver interface anymore).
Max
signature.asc
Description: OpenPGP digital signature
- [Qemu-block] [PATCH v4 1/7] iotests: Prefer null-co over null-aio, (continued)
- [Qemu-block] [PATCH v4 1/7] iotests: Prefer null-co over null-aio, Max Reitz, 2019/09/17
- [Qemu-block] [PATCH v4 2/7] iotests: Allow skipping test cases, Max Reitz, 2019/09/17
- [Qemu-block] [PATCH v4 3/7] iotests: Use case_skip() in skip_if_unsupported(), Max Reitz, 2019/09/17
- [Qemu-block] [PATCH v4 4/7] iotests: Let skip_if_unsupported accept a function, Max Reitz, 2019/09/17
- [Qemu-block] [PATCH v4 5/7] iotests: Test driver whitelisting in 093, Max Reitz, 2019/09/17
- Re: [Qemu-block] [Qemu-devel] [PATCH v4 5/7] iotests: Test driver whitelisting in 093, John Snow, 2019/09/18
- [Qemu-block] [PATCH v4 6/7] iotests: Test driver whitelisting in 136, Max Reitz, 2019/09/17
- [Qemu-block] [PATCH v4 7/7] iotests: Cache supported_formats(), Max Reitz, 2019/09/17