Re: How to generate test reports?

[Joe Buck <jbuck@synopsys.com>]

I wrote:

> If this script were in the source and documented as the standard way
> of reporting test results, we could then automate the processing of
> test reports (since they all would have the same format).

Looking at Alexandre's script, it requires that the .sum and .log files
be copied and rearranged (alternatively a set of symbolic links can be
used).  Other than that problem it is very nice.

It would be nice if it had an option that would just take the root of
a build tree (the directory in which configure is run), and it then
used, say

find $build_tree -type f -name '*.sum' -print

to find the summary files.  It could read config.status to get the
configure arguments, rather than requiring the user to make a separate
file (though a separate file to allow extra information might be nice).

The idea is to make the process as simple as

./configure [options]
make bootstrap-lean
make -k check
make mail_report

No muss, no fuss.  However, if this is done, we'd want a different address
besides egcs to send the report to.