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

[Julian S. <js...@ac...>]

> It doesn't try and work out pass/fail at the moment - it just sends
> the last 20 lines of the output ;-) Strictly speaking none of them
> pass as they all fail at least one regression test at the moment.

We could do with better logic for figuring out the text to be
mailed to the list.  What I would like to see is:

- if the build failed before regression tests, the last 20 or so
  lines of build log, so we can see why it failed.  As per
  last night's failed R H 7.2 build.

- if the build succeeds, then I'd like to see the entire summary
  results of the regression tests, not just the last 20 lines.
  That is, I'd want to see the line
  == N tests, N stderr failures, N stdout failures =============
  and everything thereafter.

Another shortcoming of the existing code is that it doesn't stop
if something breaks, eg if the cvs co fails, it keeps going anyway.
This should be fixed.

My only slight hesitation about putting this stuff in cvs is that
anybody can run tests and so swamp the list with messages.  But I
guess we can deal with that if it happens.

Re filtering (Ashley's original question) things we could do are:

* set up a new mail list "val...@li..."
  and send all autobuild messages there.  I'd prefer not to do this
  as it would require new potential contributors to be aware of,
  and subscribe to, the list.

* include a phrase like "valgrind-nightly" in the message header
  or body, which can easily be spotted by mail clients?  I would
  prefer this.

J