This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Test results on 2.6.28-rc8
- From: Kris Van Hees <kris dot van dot hees at oracle dot com>
- To: Mark Wielaard <mjw at redhat dot com>
- Cc: wenji dot huang at oracle dot com, systemTAP <systemtap at sources dot redhat dot com>, "VAN HEES,KRIS" <kris dot van dot hees at oracle dot com>, "ZANNONI,ELENA" <ELENA dot ZANNONI at oracle dot com>
- Date: Thu, 18 Dec 2008 10:51:04 -0500
- Subject: Re: Test results on 2.6.28-rc8
- References: <4949C383.7080507@oracle.com> <1229611756.3441.34.camel@dijkstra.wildebeest.org>
Mark,
The .sum file is now available for every systemtap_snapshot reported on labrat.
Just look for the 'Download build log' link. Note that it only contains the
.sum file information. I have found the .log very useful in the past for
tracking down test failures, but past discussion within the systemtap group
resulted in objections against using the .log file. If you prefer to have
the .log available, we can definitely start doing that going forward (as we
used to do that in the past anyway).
Cheers,
Kris
On Thu, Dec 18, 2008 at 03:49:16PM +0100, Mark Wielaard wrote:
> Hi Wenji,
>
> On Thu, 2008-12-18 at 11:29 +0800, Wenji Huang wrote:
> > Test results on 2.6.28-rc8.
> > Seems problem with backtrace/context.
> >
> > ------------------------------------------------------------------------------
> > Package: systemtap_snapshot
> > (0.8/0.131-master(04844b33)-2.6.28_rc8-snapshot)
> >
> > Previous build: 2008/12/01 23:34:19 - 2008/12/01 23:34:19
> > Current build: 2008/12/10 16:01:09 - 2008/12/10 16:01:09
> > Host: rctest-32
> > Platform: Linux 2.6.28-rc8 i386 (EL4U6) (before: Linux 2.6.28-rc7
> > i386 (EL4U6))
> > URL:
> > http://build.alchar.org/cgi/showBuild?host=rctest-32&pkg=systemtap_snapshot&date=20081210-160109
> > First failure: test
> > Test result: 829: 757 +, 44 -, 28 S, 0 E (before: 816: 727 +, 61 -,
> > 28 S, 0 E)
>
> The above URL doesn't seem to contain the full testsuite
> systemtap.log/.sum files. Could you post them, so we can inspect the
> specific failures?
>
> Thanks,
>
> Mark
>