Re: [PULL 0/8] Block layer patches

[Vladimir Sementsov-Ogievskiy]

28.01.2021 21:19, Peter Maydell wrote:
> On Wed, 27 Jan 2021 at 19:58, Kevin Wolf <kwolf@redhat.com> wrote:
> > The following changes since commit bf159f0bdc7b8e7aa8342dedb3829ca744c1b612:
> >
> >    Merge remote-tracking branch 
> > 'remotes/edgar/tags/edgar/xilinx-next-2021-01-27.for-upstream' into staging 
> > (2021-01-27 17:40:25 +0000)
> >
> > are available in the Git repository at:
> >
> >    git://repo.or.cz/qemu/kevin.git tags/for-upstream
> >
> > for you to fetch changes up to a44be0334beae3a9affb4a3a92cc6852993d7a84:
> >
> >    iotests: rename and move 169 and 199 tests (2021-01-27 20:53:14 +0100)
> >
> > ----------------------------------------------------------------
> > Block layer patches:
> >
> > - Fix crash on write to read-only devices
> > - iotests: Rewrite 'check' in Python, get rid of 'groups' and allow
> >    non-numeric test case names
> >
> > ----------------------------------------------------------------
>
> I somehow failed to notice before applying this, but this
> breaks 'make check' on the netbsd and freebsd VMs.
>
> As usual the build log is pretty opaque, but this looks like the
> probable culprit:
>
> env: python3: No such file or directory
> gmake: *** [/home/qemu/qemu-test.nU2bcG/src/tests/Makefile.include:144:
> check-block] Error 1
>
> The python in the netbsd VM is /usr/pkg/bin/python3.7. Something
> seems to be ignoring the --python= passed into our configure
> and assuming that "python3" is always a valid executable.

Seems, that's shows that the fact that "PYTHON" variable in check-block.sh 
works for me doesn't mean that it works everywhere.. My fault, I look closer tomorrow.

--
Best regards,
Vladimir