From: Peter Maydell <peter.maydell@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: Eduardo Habkost <eduardo@habkost.net>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
Hanna Reitz <hreitz@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PULL 0/4] Python patches
Date: Thu, 3 Feb 2022 16:20:30 +0000 [thread overview]
Message-ID: <CAFEAcA_OXJ6C1UTFXiy6x1gp4VRmaWQY7ntU8N-3-O+TGcsKQQ@mail.gmail.com> (raw)
In-Reply-To: <20220203015946.1330386-1-jsnow@redhat.com>
On Thu, 3 Feb 2022 at 01:59, John Snow <jsnow@redhat.com> wrote:
>
> The following changes since commit 47cc1a3655135b89fa75c2824fbddd29df874612:
>
> Merge remote-tracking branch 'remotes/kwolf-gitlab/tags/for-upstream' into staging (2022-02-01 19:48:15 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/jsnow/qemu.git tags/python-pull-request
>
> for you to fetch changes up to b0b662bb2b340d63529672b5bdae596a6243c4d0:
>
> python/aqmp: add socket bind step to legacy.py (2022-02-02 14:12:22 -0500)
>
> ----------------------------------------------------------------
> Python patches
>
> Peter: I expect this to address the iotest 040,041 failures you observed
> on NetBSD. If it doesn't, let me know.
I still see this one, which is different from the 040,041 stuff,
and where 'make check' is for some reason giving a lot less useful
detail. (This is a prexisting intermittent from before this patchset).
[etc]
▶ 175/704 /io/channel/pipe/sync
OK
▶ 175/704 /io/channel/pipe/async
OK
175/704 qemu:unit / test-io-channel-file
OK 0.11s 5 subtests passed
177/704 qemu:unit / test-io-channel-tls
RUNNING
>>> G_TEST_BUILDDIR=/home/qemu/qemu-test.yiYr4m/build/tests/unit MALLOC_PERTURB_=5 G_TEST_SRCDIR=/home/qemu/qemu-test.yiYr4m/src/tests/unit /home/
qemu/qemu-test.yiYr4m/build/tests/unit/test-io-channel-tls --tap -k
▶ 176/704 /io/channel/socket/ipv4-sync
OK
▶ 176/704 /io/channel/socket/ipv4-async
OK
▶ 176/704 /io/channel/socket/ipv4-fd
OK
▶ 176/704 /io/channel/socket/ipv6-sync
OK
▶ 176/704 /io/channel/socket/ipv6-async
OK
▶ 176/704 /io/channel/socket/unix-sync
OK
▶ 176/704 /io/channel/socket/unix-async
OK
▶ 176/704 /io/channel/socket/unix-fd-pass
OK
▶ 176/704 /io/channel/socket/unix-listen-cleanup
OK
176/704 qemu:unit / test-io-channel-socket
OK 0.13s 9 subtests passed
▶ 1/1 qcow2 qsd-jobs OK
1/1 qemu:block / qemu-iotests qcow2 ERROR 243.14s exit status 1
178/704 qemu:unit / test-io-task
RUNNING
>>> G_TEST_BUILDDIR=/home/qemu/qemu-test.yiYr4m/build/tests/unit MALLOC_PERTURB_=194 G_TEST_SRCDIR=/home/qemu/qemu-test.yiYr4m/src/tests/unit /hom
e/qemu/qemu-test.yiYr4m/build/tests/unit/test-io-task --tap -k
▶ 147/704 /bdrv-drain/blockjob/iothread/error/drain_subtree
OK
Summary of Failures:
1/1 qemu:block / qemu-iotests qcow2 ERROR 243.14s exit status 1
Ok: 0
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 0
Timeout: 0
Full log written to /home/qemu/qemu-test.yiYr4m/build/meson-logs/iotestslog.txt
▶ 147/704 /bdrv-drain/deletion/drain
OK
▶ 178/704 /crypto/task/complete
OK
▶ 178/704 /crypto/task/datafree
OK
[etc]
thanks
-- PMM
next prev parent reply other threads:[~2022-02-03 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 1:59 [PULL 0/4] Python patches John Snow
2022-02-03 1:59 ` [PULL 1/4] python/aqmp: Fix negotiation with pre-"oob" QEMU John Snow
2022-02-03 1:59 ` [PULL 2/4] python/machine: raise VMLaunchFailure exception from launch() John Snow
2022-02-03 1:59 ` [PULL 3/4] python: upgrade mypy to 0.780 John Snow
2022-02-03 1:59 ` [PULL 4/4] python/aqmp: add socket bind step to legacy.py John Snow
2022-02-03 16:20 ` Peter Maydell [this message]
2022-02-03 16:38 ` [PULL 0/4] Python patches John Snow
2022-02-03 16:51 ` Peter Maydell
2022-02-03 23:22 ` John Snow
2022-02-08 14:40 ` Peter Maydell
2022-02-15 17:45 ` John Snow
2022-02-15 18:00 ` Peter Maydell
2022-02-15 19:02 ` John Snow
2022-02-04 17:03 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2022-01-10 23:25 John Snow
2022-01-12 9:20 ` 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=CAFEAcA_OXJ6C1UTFXiy6x1gp4VRmaWQY7ntU8N-3-O+TGcsKQQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=eduardo@habkost.net \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--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.