[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #8 from sergstesh at yahoo dot com 2006-11-09 13:41 --- I looked into source code of 'test_summary' script and it indeed calls the 'Mail' program, the one with capital 'M'. I have never heard of it, I am familiar with 'mail' with small 'm'. On my system it's lrwxrwxrwx 1 root root 14 Jan 12 2006 /usr/bin/Mail -> ../../bin/mail . Is it OK ? I tried ../gcc-3.4.6.src/contrib/test_summary -p /dev/null -m [EMAIL PROTECTED] -f | sh - pay attention to '-f', and nothing happens. No mail is sent, no messages on screen. How can I regenerate the Email text produced by the first invokation of 'test_summary' ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #7 from sergstesh at yahoo dot com 2006-11-08 23:29 --- OK, being in /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6 directory, which is my 'obj' directory, I tried to run the 'test_summary' mentioned at the bottom of http://gcc.gnu.org/install/test.html : " 0.5 Submitting test results If you want to report the results to the GCC project, use the contrib/test_summary shell script. Start it in the objdir with srcdir/contrib/test_summary -p your_commentary.txt \ -m [EMAIL PROTECTED] |sh This script uses the Mail program to send the results, so make sure it is in your PATH. The file your_commentary.txt is prepended to the testsuite summary and should contain any special remarks you have on your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. ". Please pay attention to " This script uses the Mail program to send the results, so make sure it is in your PATH ". On my system: " [21] 1:20 [EMAIL PROTECTED]:/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6> which mail /bin/mail ". However, here's what I'm getting running the program: " ../gcc-3.4.6.src/contrib/test_summary -p /dev/null -m [EMAIL PROTECTED] | sh /usr/sbin/sendmail: No such file or directory "/ibm/home/sergei/dead.letter" 103/2351 . . . message not sent. ". So, should I file a bug against http://gcc.gnu.org/install/test.html because of 'mail' <-> /usr/sbin/sendmail discrepancy ? Anyway, I looked into /ibm/home/sergei/dead.letter file and it contains pretty much the same info I've already posted. If you insist, I can install /usr/sbin/sendmail and try again. Maybe you already have enough info to tell me which of the tests fail due to: 1) problems in the compiler; 2) problems in glibc; 3) problems in the tests themselves ? Thanks in advance. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-11-08 22:48 --- Some failures are also due to faulty glibc, etc. and not related to GCC. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-11-08 22:47 --- > 1) do the failing tests indicate problems in gcc ? Depends on the failure. > 2) do the failing test fail because they themselves are faulty ? Depends on the failures. You might want to look at http://gcc.gnu.org/gcc-3.4/buildstat.html And the other buildstat.html for the other releases. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #4 from sergstesh at yahoo dot com 2006-11-08 22:43 --- I read the document: http://gcc.gnu.org/install/test.html, but it doesn't answer my questions. If you need test results reported through the suggested srcdir/contrib/test_summary -p your_commentary.txt \ -m [EMAIL PROTECTED] |sh command, I can do this, but will you answer the " 1) do the failing tests indicate problems in gcc ? 2) do the failing test fail because they themselves are faulty ? " questions ? If not, why should I bother in the first place ? If yes, what info other than the one produced by srcdir/contrib/test_summary -p your_commentary.txt \ -m [EMAIL PROTECTED] |sh do you need ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-11-08 22:00 --- (In reply to comment #2) > I do not understand you comment. Documented at: http://gcc.gnu.org/install/test.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #2 from sergstesh at yahoo dot com 2006-11-08 21:44 --- I do not understand you comment. That is, from 'make' manpage: " -k Continue as much as possible after an error. While the target that failed, and those that depend on it, cannot be remade, the other dependencies of these targets can be processed all the same. " - my point was that there were failing tests. And my implied questions were: 1) do the failing tests indicate problems in gcc ? 2) do the failing test fail because they themselves are faulty ? After 'make check': " FAIL: gcc.c-torture/execute/va-arg-25.c execution, -Os FAIL: gcc.dg/cleanup-8.c execution test FAIL: gcc.dg/cleanup-9.c execution test FAIL: gcc.dg/special/gcsec-1.c (test for excess errors) FAIL: g++.old-deja/g++.law/weak.C (test for excess errors) FAIL: abi_check ". After 'make -k check': " FAIL: gcc.c-torture/execute/va-arg-25.c execution, -Os FAIL: gcc.dg/cleanup-8.c execution test FAIL: gcc.dg/cleanup-9.c execution test FAIL: gcc.dg/special/gcsec-1.c (test for excess errors) FAIL: g++.old-deja/g++.law/weak.C (test for excess errors) FAIL: abi_check FAIL: gctest ". Could you please answer the: " 1) do the failing tests indicate problems in gcc ? 2) do the failing test fail because they themselves are faulty ? " questions ? Thanks in advance. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
[Bug testsuite/29760] 'make check' for gcc-3.4.6 fails
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-11-08 17:26 --- Use "make -k check" as documented. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760
