Re: [PATCH] qemu-iotests: move check-block back to Makefiles

2020-09-03 Thread Lukáš Doktor
Dne 02. 09. 20 v 12:21 Thomas Huth napsal(a): > On 02/09/2020 10.37, Paolo Bonzini wrote: >> On 02/09/20 10:19, Daniel P. Berrangé wrote: >>> On Wed, Sep 02, 2020 at 04:00:46AM -0400, Paolo Bonzini wrote: check-block has its own test harness, unlike every other test. If we capture its ou

Re: [PATCH] qemu-iotests: move check-block back to Makefiles

2020-09-02 Thread Alex Bennée
Paolo Bonzini writes: > check-block has its own test harness, unlike every other test. If > we capture its output, as is in general nicer to do without V=1, > there will be no sign of progress. So for lack of a better option > just move the invocation of the test back to Makefile rules. > > A

Re: [PATCH] qemu-iotests: move check-block back to Makefiles

2020-09-02 Thread Thomas Huth
On 02/09/2020 10.37, Paolo Bonzini wrote: > On 02/09/20 10:19, Daniel P. Berrangé wrote: >> On Wed, Sep 02, 2020 at 04:00:46AM -0400, Paolo Bonzini wrote: >>> check-block has its own test harness, unlike every other test. If >>> we capture its output, as is in general nicer to do without V=1, >>>

Re: [PATCH] qemu-iotests: move check-block back to Makefiles

2020-09-02 Thread Paolo Bonzini
On 02/09/20 10:19, Daniel P. Berrangé wrote: > On Wed, Sep 02, 2020 at 04:00:46AM -0400, Paolo Bonzini wrote: >> check-block has its own test harness, unlike every other test. If >> we capture its output, as is in general nicer to do without V=1, >> there will be no sign of progress. So for lack

Re: [PATCH] qemu-iotests: move check-block back to Makefiles

2020-09-02 Thread Daniel P . Berrangé
On Wed, Sep 02, 2020 at 04:00:46AM -0400, Paolo Bonzini wrote: > check-block has its own test harness, unlike every other test. If > we capture its output, as is in general nicer to do without V=1, > there will be no sign of progress. So for lack of a better option > just move the invocation of t

[PATCH] qemu-iotests: move check-block back to Makefiles

2020-09-02 Thread Paolo Bonzini
check-block has its own test harness, unlike every other test. If we capture its output, as is in general nicer to do without V=1, there will be no sign of progress. So for lack of a better option just move the invocation of the test back to Makefile rules. As a side effect, this will also fix "