[Qemu-devel] [PATCH v5 0/5] iotests: use python logging

John Snow posted 5 patches 6 years, 1 month ago
Test FreeBSD passed
Test docker-mingw@fedora passed
Test asan failed
Test docker-clang@ubuntu passed
Test checkpatch passed
Test docker-quick@centos7 passed
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20190917234549.22910-1-jsnow@redhat.com
Maintainers: Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>
There is a newer version of this series
tests/qemu-iotests/030        |   4 +-
tests/qemu-iotests/149        |   3 +-
tests/qemu-iotests/194        |   3 +-
tests/qemu-iotests/202        |   3 +-
tests/qemu-iotests/203        |   3 +-
tests/qemu-iotests/206        |   2 +-
tests/qemu-iotests/207        |   4 +-
tests/qemu-iotests/208        |   2 +-
tests/qemu-iotests/209        |   2 +-
tests/qemu-iotests/210        |   4 +-
tests/qemu-iotests/211        |   4 +-
tests/qemu-iotests/212        |   4 +-
tests/qemu-iotests/213        |   4 +-
tests/qemu-iotests/216        |   3 +-
tests/qemu-iotests/218        |   2 +-
tests/qemu-iotests/219        |   2 +-
tests/qemu-iotests/222        |   5 +-
tests/qemu-iotests/224        |   3 +-
tests/qemu-iotests/228        |   3 +-
tests/qemu-iotests/234        |   3 +-
tests/qemu-iotests/235        |   4 +-
tests/qemu-iotests/236        |   2 +-
tests/qemu-iotests/237        |   2 +-
tests/qemu-iotests/238        |   2 +
tests/qemu-iotests/242        |   2 +-
tests/qemu-iotests/245        |   1 +
tests/qemu-iotests/245.out    |  24 +++----
tests/qemu-iotests/246        |   2 +-
tests/qemu-iotests/248        |   2 +-
tests/qemu-iotests/254        |   2 +-
tests/qemu-iotests/255        |   2 +-
tests/qemu-iotests/256        |   2 +-
tests/qemu-iotests/258        |   8 +--
tests/qemu-iotests/262        |   3 +-
tests/qemu-iotests/iotests.py | 123 +++++++++++++++++++++-------------
35 files changed, 133 insertions(+), 111 deletions(-)
[Qemu-devel] [PATCH v5 0/5] iotests: use python logging
Posted by John Snow 6 years, 1 month ago
This series uses python logging to enable output conditionally on
iotests.log(). We unify an initialization call (which also enables
debugging output for those tests with -d) and then make the switch
inside of iotests.

It will help alleviate the need to create logged/unlogged versions
of all the various helpers we have made.

V5:
 - Rebased again
 - Allow Python tests to run on any platform

V4:
 - Rebased on top of kwolf/block at the behest of mreitz

V3:
 - Rebased for 4.1+; now based on main branch.

V2:
 - Added all of the other python tests I missed to use script_initialize
 - Refactored the common setup as per Ehabkost's suggestion
 - Added protocol arguments to common initialization,
   but this isn't strictly required.

John Snow (5):
  iotests: remove 'linux' from default supported platforms
  iotests: add script_initialize
  iotest 258: use script_main
  iotests: specify protocol support via initialization info
  iotests: use python logging for iotests.log()

 tests/qemu-iotests/030        |   4 +-
 tests/qemu-iotests/149        |   3 +-
 tests/qemu-iotests/194        |   3 +-
 tests/qemu-iotests/202        |   3 +-
 tests/qemu-iotests/203        |   3 +-
 tests/qemu-iotests/206        |   2 +-
 tests/qemu-iotests/207        |   4 +-
 tests/qemu-iotests/208        |   2 +-
 tests/qemu-iotests/209        |   2 +-
 tests/qemu-iotests/210        |   4 +-
 tests/qemu-iotests/211        |   4 +-
 tests/qemu-iotests/212        |   4 +-
 tests/qemu-iotests/213        |   4 +-
 tests/qemu-iotests/216        |   3 +-
 tests/qemu-iotests/218        |   2 +-
 tests/qemu-iotests/219        |   2 +-
 tests/qemu-iotests/222        |   5 +-
 tests/qemu-iotests/224        |   3 +-
 tests/qemu-iotests/228        |   3 +-
 tests/qemu-iotests/234        |   3 +-
 tests/qemu-iotests/235        |   4 +-
 tests/qemu-iotests/236        |   2 +-
 tests/qemu-iotests/237        |   2 +-
 tests/qemu-iotests/238        |   2 +
 tests/qemu-iotests/242        |   2 +-
 tests/qemu-iotests/245        |   1 +
 tests/qemu-iotests/245.out    |  24 +++----
 tests/qemu-iotests/246        |   2 +-
 tests/qemu-iotests/248        |   2 +-
 tests/qemu-iotests/254        |   2 +-
 tests/qemu-iotests/255        |   2 +-
 tests/qemu-iotests/256        |   2 +-
 tests/qemu-iotests/258        |   8 +--
 tests/qemu-iotests/262        |   3 +-
 tests/qemu-iotests/iotests.py | 123 +++++++++++++++++++++-------------
 35 files changed, 133 insertions(+), 111 deletions(-)

-- 
2.21.0


Re: [PATCH v5 0/5] iotests: use python logging
Posted by Max Reitz 6 years, 1 month ago
On 18.09.19 01:45, John Snow wrote:
> This series uses python logging to enable output conditionally on
> iotests.log(). We unify an initialization call (which also enables
> debugging output for those tests with -d) and then make the switch
> inside of iotests.
> 
> It will help alleviate the need to create logged/unlogged versions
> of all the various helpers we have made.
> 
> V5:
>  - Rebased again
>  - Allow Python tests to run on any platform
> 
> V4:
>  - Rebased on top of kwolf/block at the behest of mreitz
> 
> V3:
>  - Rebased for 4.1+; now based on main branch.
> 
> V2:
>  - Added all of the other python tests I missed to use script_initialize
>  - Refactored the common setup as per Ehabkost's suggestion
>  - Added protocol arguments to common initialization,
>    but this isn't strictly required.

I’m OK to take the series as-is (it doesn’t affect any auto tests, so we
can decide what to do about non-Linux platforms in make check at a later
point), but there seems to be something you wanted to fix up in patch 5.

(And there’s also Kevin’s pending pull request that changes a bit of
iotests.py.)

Max

Re: [PATCH v5 0/5] iotests: use python logging
Posted by John Snow 6 years, 1 month ago

On 10/4/19 11:39 AM, Max Reitz wrote:
> On 18.09.19 01:45, John Snow wrote:
>> This series uses python logging to enable output conditionally on
>> iotests.log(). We unify an initialization call (which also enables
>> debugging output for those tests with -d) and then make the switch
>> inside of iotests.
>>
>> It will help alleviate the need to create logged/unlogged versions
>> of all the various helpers we have made.
>>
>> V5:
>>  - Rebased again
>>  - Allow Python tests to run on any platform
>>
>> V4:
>>  - Rebased on top of kwolf/block at the behest of mreitz
>>
>> V3:
>>  - Rebased for 4.1+; now based on main branch.
>>
>> V2:
>>  - Added all of the other python tests I missed to use script_initialize
>>  - Refactored the common setup as per Ehabkost's suggestion
>>  - Added protocol arguments to common initialization,
>>    but this isn't strictly required.
> 
> I’m OK to take the series as-is (it doesn’t affect any auto tests, so we
> can decide what to do about non-Linux platforms in make check at a later
> point), but there seems to be something you wanted to fix up in patch 5.
> 
> (And there’s also Kevin’s pending pull request that changes a bit of
> iotests.py.)
> 
> Max
> 

Just caught up with the discussion.

It looks like Thomas took my 1/5; so I'll respin on top of his "[PATCH
0/5] Enable more iotests during "make check-block" series to catch those
improvements as they stand.

--js

Re: [PATCH v5 0/5] iotests: use python logging
Posted by Max Reitz 5 years, 8 months ago
On 12.10.19 01:39, John Snow wrote:
> Just caught up with the discussion.
> 
> It looks like Thomas took my 1/5; so I'll respin on top of his "[PATCH
> 0/5] Enable more iotests during "make check-block" series to catch those
> improvements as they stand.

Any updates on this? :)

Max

Re: [PATCH v5 0/5] iotests: use python logging
Posted by John Snow 5 years, 8 months ago

On 2/24/20 6:15 AM, Max Reitz wrote:
> On 12.10.19 01:39, John Snow wrote:
>> Just caught up with the discussion.
>>
>> It looks like Thomas took my 1/5; so I'll respin on top of his "[PATCH
>> 0/5] Enable more iotests during "make check-block" series to catch those
>> improvements as they stand.
> 
> Any updates on this? :)
> 
> Max
> 

Nope.

Well, except that I was working on job_run today and remembered that I
needed to do this. I was waiting for that discussion to die down, and
then forgetting took over.

Will attempt to resuscitate.