This affects any HTB triplet if the person runs the "contrib/test_summary"
script.
The script creates results that are not "pretty-printed" and mails them to
[EMAIL PROTECTED] which automatically generates ugly web pages.
We might improved the line spacing in the mailer script, here is an example:
---START---
/opt/gcc-4_3-build/gcc/testsuite/gfortran/../../gfortran version 4.3.0
20070523 (experimental)
=== gnat tests ===
Running target unix
FAIL: gnat.dg/address_conversion.adb execution test
=== gnat Summary ===
# of expected passes 168
# of unexpected failures 1
=== obj-c++ tests ===
Running target unix
--- END ---
I suggest it would look better if it were like this:
---START---
/opt/gcc-4_3-build/gcc/testsuite/gfortran/../../gfortran version 4.3.0
20070523 (experimental)
(Add a blank line here)
=== gnat tests ===
(Subtract a blank line here)
Running target unix
FAIL: gnat.dg/address_conversion.adb execution test
=== gnat Summary ===
# of expected passes 168
# of unexpected failures 1
(Add a blank line here)
(Add a blank line here)
=== obj-c++ tests ===
(Subtract a blank line here)
Running target unix
--- END ---
That is only a dozen line example. The _whole_ output is like that; with extra
"C/R"'s where they are not needed and too few "C/R"'s in some spots.
I realize that the output is supposed to be "machine readable", so is our ource
code. We have _standards_ for the appearance of the source, why not the output.
While this is "trivial" we should have pride in our great compiler and the
usually great results. Even if there are failures we should still present them
neatly.
See here for many examples: http://gcc.gnu.org/ml/gcc-testresults/2007-05/
--
Summary: "contrib/test_summary" script could output results more
neatly
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: testsuite
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rob1weld at aol dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32063
