From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K3s9y-0006Bg-T5 for qemu-devel@nongnu.org; Wed, 04 Jun 2008 08:32:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K3s9w-000690-OW for qemu-devel@nongnu.org; Wed, 04 Jun 2008 08:32:10 -0400 Received: from [199.232.76.173] (port=53262 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3s9w-00068k-He for qemu-devel@nongnu.org; Wed, 04 Jun 2008 08:32:08 -0400 Received: from wr-out-0506.google.com ([64.233.184.237]:56778) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K3s9w-0001jM-7m for qemu-devel@nongnu.org; Wed, 04 Jun 2008 08:32:08 -0400 Received: by wr-out-0506.google.com with SMTP id c49so11253wra.19 for ; Wed, 04 Jun 2008 05:32:07 -0700 (PDT) Message-ID: <5d6222a80806040532o4672be48y4d9e91cdadb5686c@mail.gmail.com> Date: Wed, 4 Jun 2008 09:32:07 -0300 From: "Glauber Costa" Subject: Re: [Qemu-devel] Suggestion for testing framework In-Reply-To: <48466E36.7090907@qumranet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <767386.58386.qm@web57006.mail.re3.yahoo.com> <200806032302.09778.paul@codesourcery.com> <5d6222a80806031505t15f18fe7u256514ccbdc9960@mail.gmail.com> <200806032325.02120.paul@codesourcery.com> <48466E36.7090907@qumranet.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Erik de Castro Lopo , qemu-devel@nongnu.org, "Balazs Attila-Mihaly (Cd-MaN)" On Wed, Jun 4, 2008 at 7:28 AM, Avi Kivity wrote: > Paul Brook wrote: >> >> We were talking about a tester that does periodic long running tests off >> svn trunk, and reports the results. Individual developers are not directly >> involved. >> >> > > Even that is tremendously useful. Once you identify a regression, it is > easy to bisect and pinpoint the offending patch, which also locates the > author. Not that easy, regarding bisection. Qemu does not have an as strict commit policy as the linux kernel, and you bet most of the commits won't build fine by their own. > >> You're talking about some sort of testsuite that can be distributed to all >> developers and reasonably run before every patch is submitted, which is a >> significantly different beast. >> >> I'm pretty certain the proposed tests would not be suitable for routine >> use by the majority of developers are part of normal developers. They will >> be too large, probably take a long time to run, and contain proprietary >> software that can't be redistributed. >> > > There's no need to start at the screen while the test is running. > Proprietary software can be worked around by having the user provide a CD > image and licensing keys in a configuration file. > That's a good solution, but we do have an awful lot of Free Software that covers a wide range of qemu targets, right? So even if one does not have, or does not want to run a CD, or so, it's still better than nothing at all -- Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act."