From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pkrempa@redhat.com, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] iotests: Fix up python style in 300
Date: Mon, 15 Feb 2021 18:21:43 -0500 [thread overview]
Message-ID: <39d5d446-3271-a8fd-0755-6a0fbfe24c09@redhat.com> (raw)
In-Reply-To: <20210215220518.1745469-1-eblake@redhat.com>
On 2/15/21 5:05 PM, Eric Blake wrote:
> Break some long lines, and relax our type hints to be more generic to
> any JSON, in order to more easily permit the additional JSON depth now
> possible in migration parameters. Detected by iotest 297.
>
> Fixes: ca4bfec41d56
> (qemu-iotests: 300: Add test case for modifying persistence of bitmap)
> Reported-by: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
> ---
> tests/qemu-iotests/300 | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/tests/qemu-iotests/300 b/tests/qemu-iotests/300
> index 63036f6a6e13..adb927629747 100755
> --- a/tests/qemu-iotests/300
> +++ b/tests/qemu-iotests/300
> @@ -22,7 +22,7 @@
> import os
> import random
> import re
> -from typing import Dict, List, Optional, Union
> +from typing import Dict, List, Optional
>
> import iotests
>
> @@ -30,7 +30,7 @@ import iotests
> # pylint: disable=wrong-import-order
> import qemu
>
> -BlockBitmapMapping = List[Dict[str, Union[str, List[Dict[str, str]]]]]
> +BlockBitmapMapping = List[Dict[str, object]]
>
Assuming iotest 297 didn't yap about this, I think this has the
necessary power for this file and we don't have to work any harder.
If in the future you try to treat e.g. bmap['persistent'] as a
particular kind of value (string? bool? int?) mypy will likely complain
about that a little, saying it has no insight into the type beyond "object".
If *that* becomes annoying, you can degrade this type to use 'Any'
instead of 'object' and even those checks will cease.
> mig_sock = os.path.join(iotests.sock_dir, 'mig_sock')
>
> @@ -602,7 +602,8 @@ class TestCrossAliasMigration(TestDirtyBitmapMigration):
>
> class TestAliasTransformMigration(TestDirtyBitmapMigration):
> """
> - Tests the 'transform' option which modifies bitmap persistence on migration.
> + Tests the 'transform' option which modifies bitmap persistence on
> + migration.
> """
>
> src_node_name = 'node-a'
> @@ -674,7 +675,8 @@ class TestAliasTransformMigration(TestDirtyBitmapMigration):
> bitmaps = self.vm_b.query_bitmaps()
>
> for node in bitmaps:
> - bitmaps[node] = sorted(((bmap['name'], bmap['persistent']) for bmap in bitmaps[node]))
> + bitmaps[node] = sorted(((bmap['name'], bmap['persistent'])
> + for bmap in bitmaps[node]))
>
> self.assertEqual(bitmaps,
> {'node-a': [('bmap-a', True), ('bmap-b', False)],
>
next prev parent reply other threads:[~2021-02-15 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 22:05 [PATCH] iotests: Fix up python style in 300 Eric Blake
2021-02-15 23:21 ` John Snow [this message]
2021-02-26 7:04 ` Vladimir Sementsov-Ogievskiy
2021-03-01 7:58 ` Markus Armbruster
2021-03-01 16:50 ` John Snow
2021-02-26 7:03 ` Vladimir Sementsov-Ogievskiy
2021-03-01 10:45 ` Kevin Wolf
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=39d5d446-3271-a8fd-0755-6a0fbfe24c09@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).