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 of a better option >> just move the invocation of the test back to Makefile rules. > > I expect the correct long term solution here is to stop using the > check-block.sh script. Instead have code which sets up each > of the I/O tests as an explicit test target in meson. We could > use meson's test grouping features too.
I'm not sure, "check-acceptance" will never be integrated in Meson, and it may well be the same for "check-block". Actually I wonder if Avocado would be a better check-block.sh than check-block.sh. Paolo
