From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36009) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S60zY-0005O0-29 for qemu-devel@nongnu.org; Fri, 09 Mar 2012 09:40:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S60zR-00057k-Am for qemu-devel@nongnu.org; Fri, 09 Mar 2012 09:40:23 -0500 Received: from mx1.redhat.com ([209.132.183.28]:15929) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S60zR-00057M-2b for qemu-devel@nongnu.org; Fri, 09 Mar 2012 09:40:17 -0500 Message-ID: <4F5A164A.7040708@redhat.com> Date: Fri, 09 Mar 2012 11:40:10 -0300 From: Lucas Meneghel Rodrigues MIME-Version: 1.0 References: <4F582EDB.1040608@redhat.com> <4F58B5CB.8040503@codemonkey.ws> <20120308144958.GA25750@t420s.optimusnet> <4F58C897.5020405@codemonkey.ws> <20120308150722.GA30576@t420s.optimusnet> <4F58CCBA.9000702@codemonkey.ws> <20120308160505.GA32360@t420s.optimusnet> <4F58E67A.3050708@codemonkey.ws> <20120308175907.GA4900@t420s.optimusnet> <4F5905AA.3060304@codemonkey.ws> <20120308210209.GA11998@t420s.optimusnet> <4F59237F.6010406@codemonkey.ws> <4F593BAF.1020201@redhat.com> <4F59F3FF.9040009@codemonkey.ws> <4F59FC26.4020404@redhat.com> <4F5A1019.5020203@codemonkey.ws> In-Reply-To: <4F5A1019.5020203@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] Future goals for autotest and virtualization tests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Cleber Rosa , QEMU devel , "kvm-autotest@redhat.com" , Ademar Reis On 03/09/2012 11:13 AM, Anthony Liguori wrote: >> It is indeed a bit nerve wrecking to hear that all you can do with the >> stuff you >> have been working on the last 3 years can be done better with a dozen >> of shell >> script functions. It's similar to say that we just like to throw lines >> at a text >> editor just for the fun of it. I am sure you didn't mean it but that >> is how it >> sounded, and that's why I'd like to assure that the code there *does >> stuff*. > > Look at how this discussion started. We've been discussing testing on > qemu-devel at excruciating length and detail and have finally come to > something of a consensus. AFAIK, no one from autotest has participated > in those discussions which is fair as I'm sure ya'll don't read > qemu-devel religiously. All right, point taken. > Then we see this note that more or less declares, this is how QEMU > should do all of its testing. What reaction did you really expect there > to be? :-) It was an attempt to offer what we have rather than dictating how QEMU should do all its testing: """ One of our main goals is to provide useful tools for the qemu community, since we have a good number of tests and libraries written to perform integration/QA testing for that tool, being successfuly used by a number of QA teams that work on qemu. """ I re-read the first message I sent, and certainly did not find where we declare that this is the way QEMU should do its testing. If you judge that there's nothing interesting there for qemu, I'm fine with it. That all said, certainly I did not expect your repeated attempts to show that you can do it all better with a couple of shell script lines, oh boy, I did not.