From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH] iotests: fix 169
Date: Wed, 11 Apr 2018 18:11:57 +0200 [thread overview]
Message-ID: <e8cc4fbe-4b0e-4ab8-64ff-0c12a080e09e@redhat.com> (raw)
In-Reply-To: <90b289f4-d976-1fb7-57e2-aa02d00947d1@virtuozzo.com>
On 2018-04-11 15:05, Vladimir Sementsov-Ogievskiy wrote:
[...]
> Hmm, first type? I'm now not sure about, did I really see sha256
> mismatch, or something like this (should be error, but found bitmap):
>
> --- /work/src/qemu/up-169/tests/qemu-iotests/169.out 2018-04-11
> 15:35:10.055027392 +0300
> +++ /work/src/qemu/up-169/tests/qemu-iotests/169.out.bad 2018-04-11
> 15:58:09.300450045 +0300
> @@ -1,5 +1,20 @@
> -........
> +F.......
> +======================================================================
> +FAIL: test__not_persistent__migbitmap__offline
> (__main__.TestDirtyBitmapMigration)
> +methodcaller(name, ...) --> methodcaller object
> +----------------------------------------------------------------------
> +Traceback (most recent call last):
> + File "169", line 136, in do_test_migration
> + self.check_bitmap(self.vm_b, sha256 if persistent else False)
> + File "169", line 77, in check_bitmap
> + "Dirty bitmap 'bitmap0' not found");
> + File "/work/src/qemu/up-169/tests/qemu-iotests/iotests.py", line 389,
> in assert_qmp
> + result = self.dictpath(d, path)
> + File "/work/src/qemu/up-169/tests/qemu-iotests/iotests.py", line 348,
> in dictpath
> + self.fail('failed path traversal for "%s" in "%s"' % (path, str(d)))
> +AssertionError: failed path traversal for "error/desc" in "{u'return':
> {u'sha256':
> u'01d2ebedcb8f549a2547dbf8e231c410e3e747a9479e98909fc936e0035cf8b1'}}"
>
>
> Max, did you really seed sha256 mismatch or only something like this?
I'm pretty sure I did see mismatches.
Max
next prev parent reply other threads:[~2018-04-11 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 16:10 [Qemu-devel] [PATCH] iotests: fix 169 Vladimir Sementsov-Ogievskiy
2018-03-30 16:11 ` Vladimir Sementsov-Ogievskiy
2018-03-31 8:59 ` no-reply
2018-04-03 16:23 ` Max Reitz
2018-04-03 20:13 ` John Snow
2018-04-11 9:02 ` Vladimir Sementsov-Ogievskiy
2018-04-11 9:36 ` Vladimir Sementsov-Ogievskiy
2018-04-11 13:05 ` Vladimir Sementsov-Ogievskiy
2018-04-11 13:40 ` Vladimir Sementsov-Ogievskiy
2018-04-11 16:11 ` Max Reitz [this message]
2018-04-12 8:34 ` Vladimir Sementsov-Ogievskiy
2018-04-12 9:09 ` Vladimir Sementsov-Ogievskiy
2018-04-13 13:35 ` Max Reitz
2018-04-11 11:52 ` 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=e8cc4fbe-4b0e-4ab8-64ff-0c12a080e09e@redhat.com \
--to=mreitz@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 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).