From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/4] iotests/297: Cover tests/
Date: Fri, 14 May 2021 17:08:48 +0200 [thread overview]
Message-ID: <31e3e0fe-4cdd-e5eb-4fc5-8f4e68ac4f56@redhat.com> (raw)
In-Reply-To: <15a189aa-f906-9b4d-e206-b1c8c31b855c@redhat.com>
On 14.05.21 13:02, Max Reitz wrote:
> On 12.05.21 19:43, Max Reitz wrote:
>> v1:
>> https://lists.nongnu.org/archive/html/qemu-block/2021-03/msg01471.html
>>
>>
>> Hi,
>>
>> When reviewing Vladimir’s new addition to tests/, I noticed that 297 so
>> far does not cover named tests. That isn’t so good.
>>
>> This series makes it cover them, and because tests/ is rather sparse at
>> this point, I decided to also fix up the two tests in there that don’t
>> pass pylint’s scrutiny yet. I think it would be nice if we could keep
>> all of tests/ clean.
>>
>>
>> v2:
>> - Changed patch 2 as per Vladimir’s suggestion
>> (i.e. don’t let discards1_sha256 and all_discards_sha256 be class
>> variables at all)
>
> Thanks for the review, applied to my block branch:
>
> https://github.com/XanClic/qemu/commits/block
...and dropping again, patch 3 embarrassingly breaks
migrate-bitmaps-test. The problem seems to be that contrastingly to
pylint’s opinion, the `lambda self: mc(self)` is necessary, it can’t be
contracted to just `mc`. I suspect that `mc` (returned by
`methodcaller`) has a variable argument list, and so without the lambda,
`setattr` adds it as a argument-less function, so when it is called, it
doesn’t receive the `self` parameter. (It complains that it expected 1
argument, but got 0.)
So we need the lambda to enforce that the `self` parameter is passed.
Max
prev parent reply other threads:[~2021-05-14 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 17:43 [PATCH v2 0/4] iotests/297: Cover tests/ Max Reitz
2021-05-12 17:43 ` [PATCH v2 1/4] iotests/297: Drop 169 and 199 from the skip list Max Reitz
2021-05-12 17:43 ` [PATCH v2 2/4] migrate-bitmaps-postcopy-test: Fix pylint warnings Max Reitz
2021-05-13 10:52 ` Vladimir Sementsov-Ogievskiy
2021-05-12 17:43 ` [PATCH v2 3/4] migrate-bitmaps-test: " Max Reitz
2021-05-12 17:43 ` [PATCH v2 4/4] iotests/297: Cover tests/ Max Reitz
2021-05-14 11:02 ` [PATCH v2 0/4] " Max Reitz
2021-05-14 15:08 ` Max Reitz [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=31e3e0fe-4cdd-e5eb-4fc5-8f4e68ac4f56@redhat.com \
--to=mreitz@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).