From: Kevin Wolf <kwolf@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, fam@euphon.net,
mreitz@redhat.com, armbru@redhat.com, berrange@redhat.com,
eblake@redhat.com, den@openvz.org, vsementsov@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH v14 3/3] qcow2: list of bitmaps new test 242
Date: Mon, 18 Feb 2019 17:12:07 +0100 [thread overview]
Message-ID: <20190218161207.GD5303@dhcp-200-176.str.redhat.com> (raw)
In-Reply-To: <1549638368-530182-4-git-send-email-andrey.shinkevich@virtuozzo.com>
Am 08.02.2019 um 16:06 hat Andrey Shinkevich geschrieben:
> A new test file 242 added to the qemu-iotests set. It checks
> the format of qcow2 specific information for the new added
> section that lists details of bitmaps.
>
> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
This doesn't seem to be Python 3 compatible.
Kevin
242 [17:09:27] [17:09:29] [failed, exit status 1] - output mismatch (see 242.out.bad)
--- /home/kwolf/source/qemu/tests/qemu-iotests/242.out 2019-02-13 12:59:38.748262364 +0100
+++ /home/kwolf/source/qemu/tests/qemu-iotests/242.out.bad 2019-02-18 17:09:29.314637597 +0100
@@ -143,24 +143,9 @@
{"execute": "block-dirty-bitmap-add", "arguments": {"disabled": false, "granularity": 16384, "name": "bitmap-0", "node": "drive0", "persistent": true}}
{"return": {}}
Write an unknown bitmap flag '0x4' into a new QCOW2 image at offset 327695
-qemu-img: Could not open 'TEST_IMG': Bitmap 'bitmap-0' doesn't satisfy the constraints
-
-Unset the unknown bitmap flag '0x4' in the bitmap directory entry:
-
-image: TEST_IMG
-file format: IMGFMT
-virtual size: 1.0M (1048576 bytes)
-cluster_size: 65536
-Format specific information:
- compat: 1.1
- lazy refcounts: false
- bitmaps:
- [0]:
- flags:
- [0]: auto
- name: bitmap-0
- granularity: 16384
- refcount bits: 16
- corrupt: false
-
-Test complete
+Traceback (most recent call last):
+ File "242", line 98, in <module>
+ toggle_flag(flag_offset)
+ File "242", line 70, in toggle_flag
+ f.write(toggled)
+TypeError: a bytes-like object is required, not 'str'
Failures: 242
Failed 1 of 1 tests
next prev parent reply other threads:[~2019-02-18 16:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 15:06 [Qemu-devel] [PATCH v14 0/3] qcow2: Add list of bitmaps to ImageInfoSpecificQCow2 Andrey Shinkevich
2019-02-08 15:06 ` [Qemu-devel] [PATCH v14 1/3] bdrv_query_image_info Error parameter added Andrey Shinkevich
2019-02-08 15:06 ` [Qemu-devel] [PATCH v14 2/3] qcow2: Add list of bitmaps to ImageInfoSpecificQCow2 Andrey Shinkevich
2019-02-08 15:06 ` [Qemu-devel] [PATCH v14 3/3] qcow2: list of bitmaps new test 242 Andrey Shinkevich
2019-02-08 15:45 ` Eric Blake
2019-02-18 16:12 ` Kevin Wolf [this message]
2019-02-18 19:59 ` Andrey Shinkevich
2019-02-08 15:25 ` [Qemu-devel] [PATCH v14 0/3] qcow2: Add list of bitmaps to ImageInfoSpecificQCow2 Eric Blake
2019-02-08 15:37 ` Andrey Shinkevich
2019-02-08 15:53 ` Eric Blake
2019-02-08 16:22 ` Andrey Shinkevich
2019-02-08 16:30 ` Andrey Shinkevich
2019-02-08 15:47 ` Vladimir Sementsov-Ogievskiy
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=20190218161207.GD5303@dhcp-200-176.str.redhat.com \
--to=kwolf@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=mreitz@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).