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

[Nicholas N. <nj...@ca...>]

On Wed, 25 Feb 2004, Ashley Pittman wrote:

> On Wed, 2004-02-25 at 03:00, Tom Hughes wrote:
> > Nightly build on standard ( Red Hat 7.2 ) started at 2004-02-25 03:00:00 GMT
> >
> >    Checking out source tree  ... done
> >    Configuring               ... done
> >    Building                  ... done
> >    Running regression tests  ... done
> >
> > Last 20 lines of log.verbose follow
>
> 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 test script should go into CVS, and there should be a minimal wrapper
that checks out the HEAD and launches the test script (so that changes to
the test script propagate to everyone's machines;  hopefully the wrapper
could be so simple that people could have their own local copies that
wouldn't need updating).

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...

N