This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: test results web page
- To: dhm at paradigm dot webvision dot com, egcs at cygnus dot com
- Subject: Re: test results web page
- From: mrs at wrs dot com (Mike Stump)
- Date: Wed, 10 Jun 1998 15:48:07 -0700
> Date: Mon, 8 Jun 1998 21:04:57 -0700
> From: dave madden <dhm@paradigm.webvision.com>
> To: egcs@cygnus.com
> Sorry for the delay...I've put up an initial stab at a web page for
> collecting and displaying "make check" results.
Excellent. We have always needed this type of thing...
> You can use Netscape Navigator's file-upload facility to submit
> results from the page, and I have a mail-reading script that can
> (sometimes) make sense of the reports people send to this list.
Your directions were kinda confusing on the what to upload part. I
ran the script, redirected results to me, saved the email, and
uploaded the raw saved email message. It worked, results got in.
Though, it said someone else submitted them (:-(). I knew they were
mine because of the prefix used to configure.
> The data are stored in a PostgreSQL database running on a Sun; right
> now, you can only retrieve records by configuration target, but I'm
> open to suggestions about other useful queries.
I can go on at length about this... :-) Some of them require that you
suck up the .sum file.
1. Simple queries. Given a (host,target), find the last (by version
date of compile) results. Given (*,target), find last (by version
date of compiler) results for all hosts. Given host, find all
list of targets you have ever see results for. Given nothing,
find all hosts you've ever seen results for. Given nothing, find
all targets you've ever seen results for. Use links to allow one
to refine from those lists to get to the individual results.
2. Given a test, give a list of targets it works on, and a list of targets it
fails on.
3. Given a test and a target, give a list (date sorted) of pass|fail
status.
Thanks for your work.