From: Max Reitz <mreitz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] qemu-iotests 134 broken?
Date: Mon, 20 Jul 2015 20:37:36 +0200 [thread overview]
Message-ID: <55AD3FF0.7050904@redhat.com> (raw)
In-Reply-To: <20150720180323.GA19578@stefanha-thinkpad.redhat.com>
On 20.07.2015 20:03, Stefan Hajnoczi wrote:
> I'm getting the following failure on qemu.git/master. Is anyone already
> working on this?
>
> 134 5s ... - output mismatch (see 134.out.bad)
> --- /home/stefanha/qemu/tests/qemu-iotests/134.out 2015-07-10 11:45:40.491395644 +0100
> +++ 134.out.bad 2015-07-20 19:01:23.953969973 +0100
> @@ -31,6 +31,7 @@
> You can use 'qemu-img convert' to convert your image to an unencrypted one.
> Disk image 'TEST_DIR/t.qcow2' is encrypted.
> password:
> +Pattern verification failed at offset 0, 134217728 bytes
Hi Stefan,
That should be fixed in master thanks to
http://lists.nongnu.org/archive/html/qemu-block/2015-07/msg00373.html.
Max
next prev parent reply other threads:[~2015-07-20 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 18:03 [Qemu-devel] qemu-iotests 134 broken? Stefan Hajnoczi
2015-07-20 18:37 ` Max Reitz [this message]
2015-07-20 20:07 ` Stefan Hajnoczi
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=55AD3FF0.7050904@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.