From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPCtw-00077p-Gy for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:00:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPCtp-00072W-GN for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:00:17 -0400 Received: from [199.232.76.173] (port=33345 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPCtp-00072H-9d for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:00:13 -0400 Received: from verein.lst.de ([213.95.11.210]:57332) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1MPCto-0008KX-Nw for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:00:13 -0400 Date: Fri, 10 Jul 2009 12:00:09 +0200 From: Christoph Hellwig Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: make a few more tests generic Message-ID: <20090710100009.GA6028@lst.de> References: <20090708194143.GA14640@lst.de> <4A55BF62.9070702@redhat.com> <20090709132513.GA13722@lst.de> <4A56F22A.8030406@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A56F22A.8030406@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: Anthony Liguori , Christoph Hellwig , qemu-devel@nongnu.org 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.