From: Connor Kuehl <ckuehl@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org, jsnow@redhat.com
Subject: [PATCH 0/1] iotests: fix 051.out expected output after error
Date: Thu, 18 Mar 2021 15:09:48 -0500 [thread overview]
Message-ID: <20210318200949.1387703-1-ckuehl@redhat.com> (raw)
Oops, sorry about the churn. I can see why this would have caused a
failure but I'm surprised I can't reproduce this when I run the test
locally.
Christian, would you be willing to test this patch out as a quick sanity
check too?
Connor Kuehl (1):
iotests: fix 051.out expected output after error text touchups
tests/qemu-iotests/051.out | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-18 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 20:09 Connor Kuehl [this message]
2021-03-18 20:09 ` [PATCH 1/1] iotests: fix 051.out expected output after error text touchups Connor Kuehl
2021-03-19 7:43 ` Christian Borntraeger
2021-03-23 23:22 ` John Snow
2021-03-25 15:17 ` [PATCH 0/1] iotests: fix 051.out expected output after error Max Reitz
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=20210318200949.1387703-1-ckuehl@redhat.com \
--to=ckuehl@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).