This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
reporting results even with bootstrap failure
- To: gcc at gcc dot gnu dot org
- Subject: reporting results even with bootstrap failure
- From: Brad Lucier <lucier at math dot purdue dot edu>
- Date: Thu, 5 Jul 2001 03:21:36 -0500 (EST)
- Cc: lucier at math dot purdue dot edu (Brad Lucier)
The trunk has not bootstrapped for a while on alphaev6-unknown-linux-gnu
nor on sparc-sun-solaris2.8, yet this is not reflected in the
gcc-testresults mail list.
I was wondering if anyone might be interested in modifying the
contrib/test_summary script to, say, send a report to
gcc-testresults@gcc.gnu.org even when the bootstrap failed, with
the command that failed during bootstrap together with the following
error messages. (This would be hard to impossible with a parallel
build, but I usually do a plain "make bootstrap >>& build.log" if the
parallel bootstrap failed just to see if it's a dependency problem.)
Bootstrap failures might be noticed more if they appeared in the
gcc-testresults mail list.
Brad Lucier