From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Peter Maydell <peter.maydell@linaro.org>, Kevin Wolf <kwolf@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL 0/8] Block layer patches
Date: Thu, 28 Jan 2021 23:13:59 +0300 [thread overview]
Message-ID: <9d874f5d-3d2c-067f-b3e4-55cddc48a670@virtuozzo.com> (raw)
In-Reply-To: <CAFEAcA_3Tcyx5WJazSx2kMxaipAm8B4t2nivKoyVwr53Yd-iDw@mail.gmail.com>
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
prev parent reply other threads:[~2021-01-28 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 19:57 [PULL 0/8] Block layer patches Kevin Wolf
2021-01-27 19:57 ` [PULL 1/8] block: Separate blk_is_writable() and blk_supports_write_perm() Kevin Wolf
2021-01-27 19:57 ` [PULL 2/8] virtio-scsi-test: Test writing to scsi-cd device Kevin Wolf
2021-01-27 19:57 ` [PULL 3/8] iotests: 146: drop extra whitespaces from .out file Kevin Wolf
2021-01-27 19:57 ` [PULL 4/8] iotests: add findtests.py Kevin Wolf
2021-01-27 19:57 ` [PULL 5/8] iotests: add testenv.py Kevin Wolf
2021-01-27 19:57 ` [PULL 6/8] iotests: add testrunner.py Kevin Wolf
2021-01-27 19:57 ` [PULL 7/8] iotests: rewrite check into python Kevin Wolf
2021-01-27 19:57 ` [PULL 8/8] iotests: rename and move 169 and 199 tests Kevin Wolf
2021-01-28 13:58 ` [PULL 0/8] Block layer patches Peter Maydell
2021-01-28 18:19 ` Peter Maydell
2021-01-28 20:13 ` Vladimir Sementsov-Ogievskiy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d874f5d-3d2c-067f-b3e4-55cddc48a670@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.