On Thu, Feb 3, 2022 at 11:52 AM Peter Maydell <peter.mayd...@linaro.org> wrote: > > On Thu, 3 Feb 2022 at 16:38, John Snow <js...@redhat.com> wrote: > > > On Thu, Feb 3, 2022, 11:20 AM Peter Maydell <peter.mayd...@linaro.org> > > wrote: > >> Summary of Failures: > >> > >> 1/1 qemu:block / qemu-iotests qcow2 ERROR 243.14s exit status 1
I'm not too familiar with this new test runner, yet. (Is this error even anything to do with the python lib? I guess I can't rule it out...) I just got a clean run of 'make vm-build-netbsd', so I'm using that output as reference and making some guesses. If I search the output for 'qcow2', I see the following output (with possibly many lines between each hit): 1/1 qemu:block / qemu-iotests qcow2 RUNNING >>> MALLOC_PERTURB_=205 PYTHON=/usr/pkg/bin/python3.7 /bin/sh >>> /home/qemu/qemu-test.lj6FNa/build/../src/tests/qemu-iotests/../check-block.sh >>> qcow2 ▶ 1/1 qcow2 001 OK ▶ 1/1 qcow2 002 OK ▶ 1/1 qcow2 004 OK ... and so on and so forth ... ▶ 1/1 qcow2 299 OK ▶ 1/1 qcow2 313 SKIP ▶ 1/1 qcow2 nbd-qemu-allocation SKIP ▶ 1/1 qcow2 qsd-jobs OK 1/1 qemu:block / qemu-iotests qcow2 OK 176.35s 74 subtests passed I tried modifying 040 to fail on purpose, and I see: ▶ 1/1 qcow2 039 OK ▶ 1/1 qcow2 040 FAIL ▶ 1/1 qcow2 041 OK [...] ▶ 1/1 qcow2 nbd-qemu-allocation OK ▶ 1/1 qcow2 qsd-jobs OK 1/1 qemu:block / qemu-iotests qcow2 ERROR 106.06s exit status 1 Summary of Failures: 1/1 qemu:block / qemu-iotests qcow2 ERROR 106.06s exit status 1 I don't think I see it on the output you mailed, but can you point out which test is failing, at least? Grepping for 'FAIL' should be helpful. --js