From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:45219)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1QV3PK-0002x0-OG
	for qemu-devel@nongnu.org; Fri, 10 Jun 2011 11:14:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1QV3PJ-00083H-8D
	for qemu-devel@nongnu.org; Fri, 10 Jun 2011 11:13:58 -0400
Received: from mx1.redhat.com ([209.132.183.28]:52345)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1QV3PI-00083C-VR
	for qemu-devel@nongnu.org; Fri, 10 Jun 2011 11:13:57 -0400
Date: Fri, 10 Jun 2011 12:13:51 -0300
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20110610121351.387d2840@doriath>
In-Reply-To: <4DF232AD.1010603@codemonkey.ws>
References: <20110609154704.71665a02@doriath> <4DF11945.7000108@us.ibm.com>
	<20110609170241.1ba7fde6@doriath>
	<4DF1518C.5030101@linux.vnet.ibm.com>
	<20110610115508.05b65b4e@doriath> <4DF232AD.1010603@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] gtester questions/issues
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>, Stefan Hajnoczi <stefanha@gmail.com>, Michael Roth <mdroth@linux.vnet.ibm.com>, Markus Armbruster <armbru@redhat.com>

On Fri, 10 Jun 2011 10:05:17 -0500
Anthony Liguori <anthony@codemonkey.ws> wrote:

> On 06/10/2011 09:55 AM, Luiz Capitulino wrote:
> > On Thu, 09 Jun 2011 18:04:44 -0500
> >> You kind of get the desired behavior if you run the test via something like:
> >>
> >> gtester -k -o test.xml test-visiter
> >>
> >> The gtester utility will log the return code after a test bombs, then
> >> restart and skip to the test following the one that bombed. And I'm sure
> >> gtester-report can process the resulting test.xml in manner similar to
> >> check...
> >
> > Ok, that makes the problem less worse and I agree it's possible to cook
> > a workaround for it. But IMO, glib's test framework is flawed. You just
> > can't require developers to run two additional utilities and dump xml so
> > that they can know a particular test exploded.
> 
> It all happens automagically during make check.  I don't understand what 
> the problem here is.

That's the "I agree it's possible to cook a workaround for it" part. But of
course that we have to fix gtester-report first. It doesn't work today and it
only knows how to dump HTML.