From: Peter Maydell <peter.maydell@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL 0/2] block: Fix iotests to respect configured Python binary
Date: Mon, 1 Feb 2021 21:43:16 +0000 [thread overview]
Message-ID: <CAFEAcA8fNJN6Rr7jDkHkJm2Jn8w_7UE77mzVF0H6H-ndGc-P8Q@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9otR2QS7EvH6vjJb+sePyiQ2jpO8bGkL12sG6Vt_Gm5A@mail.gmail.com>
On Fri, 29 Jan 2021 at 17:22, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Fri, 29 Jan 2021 at 16:13, Peter Maydell <peter.maydell@linaro.org> wrote:
> >
> > On Fri, 29 Jan 2021 at 14:52, Kevin Wolf <kwolf@redhat.com> wrote:
> > > ----------------------------------------------------------------
> > > Block layer patches:
> > >
> > > - Fix iotests to respect configured Python binary
> > >
> > > ----------------------------------------------------------------
> >
> > This is definitely better so I'm going to apply it, but it seems
> > to reveal a pile of iotest failures on FreeBSD:
>
> These seem to be intermittent -- a rerun was fine.
Intermittent, but not very intermittent -- I've just run about
three lots of the NetBSD vm test run in a row trying to get a
pass through, but something in iotests dies every time :-(
thanks
-- PMM
next prev parent reply other threads:[~2021-02-01 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 14:52 [PULL 0/2] block: Fix iotests to respect configured Python binary Kevin Wolf
2021-01-29 14:52 ` [PULL 1/2] iotests/testrunner: fix recognition of python tests Kevin Wolf
2021-01-29 14:52 ` [PULL 2/2] tests/Makefile.include: export PYTHON for check-block.sh Kevin Wolf
2021-01-29 16:13 ` [PULL 0/2] block: Fix iotests to respect configured Python binary Peter Maydell
2021-01-29 17:17 ` Kevin Wolf
2021-02-01 8:36 ` Vladimir Sementsov-Ogievskiy
2021-01-29 17:22 ` Peter Maydell
2021-02-01 21:43 ` Peter Maydell [this message]
2021-02-02 9:47 ` Peter Maydell
2021-02-02 11:41 ` Kevin Wolf
2021-02-02 12:43 ` Vladimir Sementsov-Ogievskiy
2021-02-02 13:44 ` Peter Maydell
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=CAFEAcA8fNJN6Rr7jDkHkJm2Jn8w_7UE77mzVF0H6H-ndGc-P8Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=kwolf@redhat.com \
--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.