qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Max Reitz <mreitz@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	QingFeng Hao <haoqf@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH for-2.12 v2] qemu-iotests: update 185 output
Date: Tue, 10 Apr 2018 16:35:51 +0200	[thread overview]
Message-ID: <20180410143551.GF7026@localhost.localdomain> (raw)
In-Reply-To: <20180410081158.GA20090@stefanha-x1.localdomain>

[-- Attachment #1: Type: text/plain, Size: 689 bytes --]

Am 10.04.2018 um 10:11 hat Stefan Hajnoczi geschrieben:
> On Wed, Apr 04, 2018 at 06:16:12PM +0200, Max Reitz wrote:
> > On 2018-04-04 17:01, Stefan Hajnoczi wrote:
> >  === Start mirror job and exit qemu ===
> > 
> > This seems to be independent of whether there is actually data on
> > TEST_IMG (the commit source), so something doesn't seem quite right with
> > the block job throttling here...?
> 
> I've been playing around with this test failure.  Let's leave it broken
> (!) in QEMU 2.12 because this test has uncovered a block job ratelimit
> issue that's not a regression.  The fix shouldn't be rushed.

Makes sense.

Thanks, applied to the block branch.

Kevin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2018-04-10 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 15:01 [Qemu-devel] [PATCH for-2.12 v2] qemu-iotests: update 185 output Stefan Hajnoczi
2018-04-04 15:40 ` Eric Blake
2018-04-04 16:16 ` Max Reitz
2018-04-09  7:24   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-10  8:11   ` [Qemu-devel] " Stefan Hajnoczi
2018-04-10 14:35     ` Kevin Wolf [this message]
2018-04-11 10:32     ` Max Reitz
2018-04-09  1:58 ` QingFeng Hao

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=20180410143551.GF7026@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=haoqf@linux.vnet.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).