[Buildbot-devel] parsing googletests, collecting stats

[Benoît Allard]

> -----Original Message-----
> From: Dmitry Nezhevenko [mailto:dion at dion.org.ua]
> Sent: Wednesday, October 17, 2012 2:03 PM
> To: buildbot-devel at lists.sourceforge.net
> Subject: Re: [Buildbot-devel] parsing googletests, collecting stats
> 
> On Wed, Oct 17, 2012 at 11:41:27AM +0200, Benoît Allard wrote:
> > You're talking about Google C++ Testing Framework [1], right ?
> >
> > We do have a custom step for that. The trick is to call the testsuite with
> an extra::
> >
> >   --gtest_output=xml:testoutput.xml
> >
> > And add that testoutput.xml to your ``logfiles`` with something like::
> >
> >   kwargs['logfiles'] = {'xml': 'testoutput.xml'}
> >
> 
> It's still a bit dangerous. Imagine that gtest will just crash. In such
> case XML file will be broken. That's why I suggest to ignore XML output
> itself and parse stdout.

Fair enough, if you can share your step once implemented, I'm interested.

> 
> Another issue is how to deal with timed out tests. If you've just one
> gtest executable, it's enough to just set build step timeout.
> 
> We're actually finding all executables named '*_gTest' and executing them
> using script on buildslave. This script also implements own timeout
> handling.

Just thinking ... then your script could also parse the stdout and generate JSON / YAML for buildbot to be even easier to parse. Or even adds the results to your test-storage database ...

Regards,
Benoît.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6467 bytes
Desc: not available
URL: <http://buildbot.net/pipermail/devel/attachments/20121017/0363b923/attachment.bin>