From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: make a few more tests generic
Date: Fri, 10 Jul 2009 12:00:09 +0200 [thread overview]
Message-ID: <20090710100009.GA6028@lst.de> (raw)
In-Reply-To: <4A56F22A.8030406@redhat.com>
On Fri, Jul 10, 2009 at 09:47:54AM +0200, Kevin Wolf wrote:
> Christoph Hellwig schrieb:
> > On Thu, Jul 09, 2009 at 11:58:58AM +0200, Kevin Wolf wrote:
> >> Christoph Hellwig schrieb:
> >>> Pretend that a non-implemented check is always successful and thus allow
> >>> various tests that were qcow2-specific before to be generic.
> >> Looks good in general. However, vmdk and vpc fail test case 011 for me.
> >> Not sure yet where the problem actually is, there seems to be no qemu-io
> >> output at all for these.
> >
> > They pass for me. So I guess we have a problem somewhere that we'll
> > eventually need to investigate.
>
> This problem has already be found. Avi's patch from almost three weeks
> ago fixes it.
Ah, that explains why I don't see it. I kept my local alternative fix
around in my quilt stack.
> It really starts to get annoying. How am I supposed to work with commits
> only every other week (which is bad enough) and then patches are
> forgotten and probably won't be merged before another two weeks? I guess
> I should manage some local tree with fixes myself and move away from
> basing my work on git master...
Yeah, working on qemu has been quite a challenge for me due to this,
too. We can try to setup some sort of staging development tree.
next prev parent reply other threads:[~2009-07-10 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 19:41 [Qemu-devel] [PATCH] qemu-iotests: make a few more tests generic Christoph Hellwig
2009-07-09 9:58 ` Kevin Wolf
2009-07-09 13:25 ` Christoph Hellwig
2009-07-10 7:47 ` Kevin Wolf
2009-07-10 10:00 ` Christoph Hellwig [this message]
2009-07-10 12:50 ` Anthony Liguori
2009-07-10 13:10 ` Kevin Wolf
2009-07-10 13:34 ` Christoph Hellwig
2009-07-10 13:39 ` Anthony Liguori
2009-07-10 14:27 ` Christoph Hellwig
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=20090710100009.GA6028@lst.de \
--to=hch@lst.de \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--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).