From: John Snow <jsnow@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Max Reitz <mreitz@redhat.com>
Cc: Connor Kuehl <ckuehl@redhat.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: iotest 051 failure on s390
Date: Thu, 18 Mar 2021 15:40:05 -0400 [thread overview]
Message-ID: <1976d02d-bb1f-99fc-1516-2f1db2102682@redhat.com> (raw)
In-Reply-To: <a574a10b-541f-ea49-9514-027b4a471e2a@de.ibm.com>
On 3/18/21 12:32 PM, Christian Borntraeger wrote:
> On s390 with latest master I do get
>
> 051 fail [17:30:00] [17:30:05] 5.4s output
> mismatch (see 051.out.bad)
> --- /home/cborntra/REPOS/qemu/tests/qemu-iotests/051.out
> +++ 051.out.bad
> @@ -61,13 +61,13 @@
> (qemu) quit
>
> Testing: -drive file=TEST_DIR/t.qcow2,node-name=123foo
> -QEMU_PROG: -drive file=TEST_DIR/t.qcow2,node-name=123foo: Invalid node
> name
> +QEMU_PROG: -drive file=TEST_DIR/t.qcow2,node-name=123foo: Invalid
> node-name: '123foo'
>
> Testing: -drive file=TEST_DIR/t.qcow2,node-name=_foo
> -QEMU_PROG: -drive file=TEST_DIR/t.qcow2,node-name=_foo: Invalid node name
> +QEMU_PROG: -drive file=TEST_DIR/t.qcow2,node-name=_foo: Invalid
> node-name: '_foo'
>
> Testing: -drive file=TEST_DIR/t.qcow2,node-name=foo#12
> -QEMU_PROG: -drive file=TEST_DIR/t.qcow2,node-name=foo#12: Invalid node
> name
> +QEMU_PROG: -drive file=TEST_DIR/t.qcow2,node-name=foo#12: Invalid
> node-name: 'foo#12'
>
Looks like we forgot to update 051.out in addition to 051.pc.out in
785ec4b1. Easy to fix.
--js
prev parent reply other threads:[~2021-03-18 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 16:32 iotest 051 failure on s390 Christian Borntraeger
2021-03-18 19:40 ` John Snow [this message]
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=1976d02d-bb1f-99fc-1516-2f1db2102682@redhat.com \
--to=jsnow@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=ckuehl@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).