This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Concerning the test_summary script
- From: mike stump <mrs at windriver dot com>
- To: chj at j-son dot org, gcc at gcc dot gnu dot org
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Mon, 25 Feb 2002 10:40:52 -0800 (PST)
- Subject: Re: Concerning the test_summary script
> Date: Sat, 23 Feb 2002 18:25:09 +0100
> To: gcc@gcc.gnu.org
> Cc: gcc-patches@gcc.gnu.org
> From: =?iso-8859-1?Q?Christian_J=F6nsson?= <chj@j-son.org>
> > The FAILs that occur carries the main information but in the e-mail
> > archive it would perhaps be a good idea to also have the "WARNING:
> > program timed out." and "ERROR: whatever: compilation failed " causes
> > to FAILs when applicable.
> Attached is a suggested patch, is this wanted or not wanted?
I have a slight preference to not want this. People that are curious
in the executive summary, don't need this information, people curious
in the details, will want the log file anyway. If people really
wants, people that want informtaion from the the full log, can set up
a list archiver, and we can create a mailing list for it, and change
the test script to also email this list with the log. Offhand, I'd
rather let people that want results for a testsuite, just run it
themselves or find someone that can for them.
Once you start including the details of why something failed, it seems
a slippry slope of ever increasing detail. The log file is that
detail, the sum is meant to not include that detail.