This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/32999] Test results script "contrib/test_summary" broken ?
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Aug 2007 05:20:16 -0000
- Subject: [Bug other/32999] Test results script "contrib/test_summary" broken ?
- References: <bug-32999-13830@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from pinskia at gcc dot gnu dot org 2007-08-06 05:20 -------
> Why do the other reports show no "FAIL" lines and no line like "# of unexpected
> failures 122" ? Was the "C" compiler _perfect_ yesterday?
If there are no failures, it will not have a line about unexpected failures
(this comes from dejagnu and not from test_summary). UNRESOLVED is not an
unexpected failure so it will not show up.
You are the only one who is seeing these extra failures so you need to look
into why that is.
Please don't mention me working on my English as your bug reports have been
weird and hard to follow as they are too verbose and mix too many different
problems in one bug report.
>I understand that reading of these results and the making of graphs to show the
> bug totals, or sending bug reports, is automated .
Not really. That has not been done for a long time now. Most people use them
to make sure a target is working or if a testcase is also failing for someone
else. And since your testresults look bad, you might as well look into why
they are so bad. Also by the way DFP is not really a feature of 4.2, only of
the trunk (for 4.3.0).
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32999