Munging gcc-testresults@ messages

[Al Stone <ahs3 at fc dot hp dot com>]

I was trying to get a clear picture of what is going
on with GCC on all the various branches and all the
various platforms.  Subscribing to gcc-testresults@
(and sending data to it) was interesting, but it was
taking too long to digest everything.  And, getting
trend data was just plain painful.

So, I wrote some python scripts to munge through all
the stuff sent to gcc-testresults@ and generate some
HTML tables for me.  The goal (based on a suggestion
from Geoff Keating) was to try to see at a glance whether
a particular branch, for a particular triplet, was
getting better, worse, or not changing.  What I came
up with can be seen at:

http://free.linux.external.hp.com/~ahs3/gcc/new_results.html

I make _no_ claims to be any good at all with HTML,
so there's probably lots of room for improvement.  And
there's probably a much simpler way to present the
material -- I'm open to suggestions.  So far, this is
working for me and if it can help out elsewhere, so
much the better.  There's roughly a month's worth of
emails from gcc-testresults@ represented right now,
and the data gets updated roughly every four hours.

BTW, all the scripts and a brief README are kept in:

http://free.linux.external.hp.com/~ahs3/gcc

Over the next couple of weeks, I'll be working on adding
plots of all results for a triplet over time, and perhaps
a way to get the historical data sent back as xml in 
response to an http query.

If this is useful, let me know and I can clean it up
to submit it for inclusion into the GCC contrib directory
(copyright assignment is on file, if needed).  If it's 
close, but could use a tweak or two, let me know that,
too (or send a patch :).

Hope this helps....

-- 
Ciao,
al
----------------------------
Al Stone
Linux & Open Source Lab
Hewlett-Packard Company
E-mail: ahs3@fc.hp.com
----------------------------