Re: [PATCH v5 0/5] iotests: use python logging

2020-02-25 Thread John Snow
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

Re: [PATCH v5 0/5] iotests: use python logging

2020-02-24 Thread Max Reitz
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

2019-10-11 Thread John Snow
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

Re: [PATCH v5 0/5] iotests: use python logging

2019-10-04 Thread Max Reitz
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

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

2019-09-17 Thread John Snow
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