From: Eric Blake <eblake@redhat.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Matthew Rosato <mjrosato@linux.ibm.com>
Subject: Re: [PATCH v4 0/5] iotests fixes
Date: Fri, 25 Sep 2026 16:46:37 -0500 [thread overview]
Message-ID: <arbrou8C1yKLZtVe@redhat.com> (raw)
In-Reply-To: <20260925194409.716498-1-farman@linux.ibm.com>
On Fri, Sep 25, 2026 at 09:44:04PM +0200, Eric Farman wrote:
> Hi Kevin, Hanna,
>
> Here is a new version of iotests fixes from our s390x systems.
> They aren't related, just came up walking through the failures.
>
> I saw you asked Eric Blake about the nbd-in-qcow2-chain patch.
> I left it as-is, but I am fine with skipping it if that's easier.
>
> I added a new patch at the end of this series, which skips the last remaining
> failure I can create out-of-the-box on s390. I had hoped that I could get
> that one to work, but it doesn't appear to be trivial.
Series:
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
next prev parent reply other threads:[~2026-09-25 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 19:44 [PATCH v4 0/5] iotests fixes Eric Farman
2026-09-25 19:44 ` [PATCH v4 1/5] iotests/nbd-in-qcow2-chain: use default machine Eric Farman
2026-09-25 19:44 ` [PATCH v4 2/5] iotests/nbd-tls-iothread: skip on non-x86 hardware Eric Farman
2026-09-25 19:44 ` [PATCH v4 3/5] iotests/fuse-truncate: skip if FUSE is not usable Eric Farman
2026-09-25 19:44 ` [PATCH v4 4/5] iotests/108: skip if fuse is unusable Eric Farman
2026-10-08 16:23 ` Eric Blake
2026-09-25 19:44 ` [PATCH v4 5/5] iotests/iothreads-nbd-export: Skip on s390 Eric Farman
2026-09-25 21:46 ` Eric Blake [this message]
2026-10-07 17:34 ` [PATCH v4 0/5] iotests fixes Eric Farman
2026-10-07 21:40 ` Eric Blake
2026-10-07 22:40 ` Eric Farman
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=arbrou8C1yKLZtVe@redhat.com \
--to=eblake@redhat.com \
--cc=farman@linux.ibm.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mjrosato@linux.ibm.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.