qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/5] vpc: Return 0 from vpc_co_create() on success
Date: Tue, 3 Sep 2019 11:06:22 +0200	[thread overview]
Message-ID: <20190903090622.GA4582@localhost.localdomain> (raw)
In-Reply-To: <20190902193320.32233-1-mreitz@redhat.com>

Am 02.09.2019 um 21:33 hat Max Reitz geschrieben:
> (v2 for “block: Let blockdev-create return 0 on success”)
> 
> Jobs are expected to return 0 on success, so this extends to
> .bdrv_co_create().  After some inspection, it turns out that vpc is the
> only block driver that may return a positive value instead (to indicate
> success).  Fix that.
> 
> Without this patch, blockdev-create is likely to fail for VPC images.
> Hence patch 5.
> 
> John indicated his preference for me to use iotests.script_main().  I
> did that; but I still wanted to retain some form of verify_protocol().
> Patch 2 adds @supported_protocols to execute_test() (and thus to
> iotests.script_main() and iotests.main()).  Then I noticed we should
> probably make all Python tests (that use either script_main() or main())
> pass something for that parameter, because it’s a bit silly to run all
> Python tests for raw when you just want to run the nbd tests (which are
> five or so).  Enter patches 3 and 4.
> 
> (There are two Python tests (093 and 136) which I didn’t change to pass
> supported_protocols, because they use null-{co,aio} as their protocol.
> As these are not actually testee protocols for the iotests, I decided to
> just keep running these tests for any protocol.)

Thanks, applied to the block branch.


      parent reply	other threads:[~2019-09-03  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 19:33 [Qemu-devel] [PATCH v2 0/5] vpc: Return 0 from vpc_co_create() on success Max Reitz
2019-09-02 19:33 ` [Qemu-devel] [PATCH v2 1/5] " Max Reitz
2019-09-02 19:33 ` [Qemu-devel] [PATCH v2 2/5] iotests: Add supported protocols to execute_test() Max Reitz
2019-09-02 19:33 ` [Qemu-devel] [PATCH v2 3/5] iotests: Restrict file Python tests to file Max Reitz
2019-09-02 19:33 ` [Qemu-devel] [PATCH v2 4/5] iotests: Restrict nbd Python tests to nbd Max Reitz
2019-09-02 19:33 ` [Qemu-devel] [PATCH v2 5/5] iotests: Test blockdev-create for vpc Max Reitz
2019-09-03  9:06 ` Kevin Wolf [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=20190903090622.GA4582@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).