From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/3] NBD patches for 2019-02-25
Date: Mon, 25 Feb 2019 09:20:12 -0600 [thread overview]
Message-ID: <20190225152015.26089-1-eblake@redhat.com> (raw)
The following changes since commit 59a568b57848b10e8a44518a889323f12ccdd8f4:
Merge remote-tracking branch 'remotes/kraxel/tags/vga-20190222-pull-request' into staging (2019-02-25 12:49:07 +0000)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2019-02-25
for you to fetch changes up to f62b3c953fae63e627cfe86333efb6294bb48a14:
iotests: avoid broken pipe with certtool (2019-02-25 08:20:17 -0600)
----------------------------------------------------------------
nbd patches for 2019-02-25
- iotest failure fixes for tests related to NBD
----------------------------------------------------------------
Andrey Shinkevich (1):
iotests: handle TypeError for Python3 in test 242
Daniel P. Berrangé (2):
iotests: ensure we print nbd server log on error
iotests: avoid broken pipe with certtool
tests/qemu-iotests/common.tls | 48 ++++++++++++++++++++++++++++---------------
tests/qemu-iotests/233 | 3 +++
tests/qemu-iotests/242 | 8 ++++++--
3 files changed, 41 insertions(+), 18 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-25 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 15:20 Eric Blake [this message]
2019-02-25 15:20 ` [Qemu-devel] [PULL 1/3] iotests: handle TypeError for Python3 in test 242 Eric Blake
2019-02-25 15:20 ` [Qemu-devel] [PULL 2/3] iotests: ensure we print nbd server log on error Eric Blake
2019-02-25 15:20 ` [Qemu-devel] [PULL 3/3] iotests: avoid broken pipe with certtool Eric Blake
2019-02-26 14:03 ` [Qemu-devel] [PULL 0/3] NBD patches for 2019-02-25 Eric Blake
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=20190225152015.26089-1-eblake@redhat.com \
--to=eblake@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).