qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PULL 0/2] block: Fix iotests to respect configured Python binary


From: Peter Maydell
Subject: Re: [PULL 0/2] block: Fix iotests to respect configured Python binary
Date: Fri, 29 Jan 2021 17:22:32 +0000

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:
> >
> > The following changes since commit 5101d00d2f1138a73344dc4833587f76d7a5fa5c:
> >
> >   Merge remote-tracking branch 
> > 'remotes/vivier2/tags/trivial-branch-for-6.0-pull-request' into staging 
> > (2021-01-29 10:10:43 +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 4cea90be62f4f15a63e1a8f7d5d0958f79fdf290:
> >
> >   tests/Makefile.include: export PYTHON for check-block.sh (2021-01-29 
> > 12:32:36 +0100)
> >
> > ----------------------------------------------------------------
> > 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. (I have a theory
that the test framework handles "QEMU process died due to the VM
running out of memory" and similar kinds of error very badly:
I semi-regularly find that when the OpenBSD, FreeBSD and NetBSD
VM jobs are running in parallel on the same machine that one
might fail but succeed on a rerun.)

Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0
for any user-visible changes.

-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]