From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:59746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ry2nE-000530-Tu for Qemu-devel@nongnu.org; Thu, 16 Feb 2012 09:58:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ry2n8-0004z2-95 for Qemu-devel@nongnu.org; Thu, 16 Feb 2012 09:58:44 -0500 Received: from mx1.redhat.com ([209.132.183.28]:61588) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ry2n7-0004yx-Vd for Qemu-devel@nongnu.org; Thu, 16 Feb 2012 09:58:38 -0500 Message-ID: <4F3D1A66.8010909@redhat.com> Date: Thu, 16 Feb 2012 16:01:58 +0100 From: Kevin Wolf MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Merging qemu-iotests into qemu.git? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: Stefan Hajnoczi , Qemu-devel@nongnu.org Hi Christoph, I just talked to Stefan about our testing, both regarding the block layer and qemu in general, and we came to the conclusion that it would probably make sense to merge qemu-iotests into qemu.git. The immediate benefit would be that we could include some short-running tests into 'make check'. Long-term we would profit from being in the same tests/ directory as all future tests for other qemu subsystems, so we could probably share quite some of the framework code. (We were initially talking about image streaming tests, which need a real VM instead of just qemu-img/io and some monitor interaction - it's easy to imagine similar cases) What do you think? Kevin