Re: [Valgrind-developers] filtering of nightly build logs

[Ashley P. <as...@pi...>]

On Wed, 2004-02-25 at 11:22, Nicholas Nethercote wrote:
> On Wed, 25 Feb 2004, Ashley Pittman wrote:
> > Is there a way to automatically filter these build logs into a different
> > folder, I know I could do it on the subject line but I want replies to
> > them to be handled correctly.  Ideally there would be some extra header
> > information that the autobuilders add but I can't see any.
> 
> We need a general way to handle these regression test messages.  Nightly
> tests are a great idea, but it's a mess at the moment, because people have
> only just started doing it.

> The script could also give a bit more info about the machine (eg. use
> uname -a, find the glibc version).  And it would be nice if specifying the
> per-machine info was simpler.  And spamming vg-dev with all the failures
> every day maybe isn't the best way to do it?  But I can't think of
> anything better...

I don't mind them coming to vg-dev, we already have the CVS commits
coming to this list and procmail manages to stash them out the way for
me quite nicely.  I find it comforting to know that things are ticking
over and I know how easy it is to break code for different platforms. 
(I'm not a valgrind developer but live in hope that I might one day be
able to use it so lurk on this list)

I'm am happy with just the distribution name and version as Tom included
in his header.  I did find it hard to tell if some of Toms builds had
passed or failed though, it looks like they passed as they don't have
any of the Make: footer but in this case they probably shouldn't include
the tail of the log file.

Ideally procmail could filter the failed and successful ones too without
having to grub inside the message contents but if there was a header to
say build-log this would just be putting something in the subject which
would be a good idea anyway.

Ashley,