From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21981 invoked by alias); 8 Nov 2006 22:43:10 -0000 Received: (qmail 21958 invoked by uid 48); 8 Nov 2006 22:43:02 -0000 Date: Wed, 08 Nov 2006 22:43:00 -0000 Message-ID: <20061108224302.21957.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/29760] 'make check' for gcc-3.4.6 fails In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "sergstesh at yahoo dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-11/txt/msg00702.txt.bz2 List-Id: ------- 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 gcc-testresults@gcc.gnu.org |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 gcc-testresults@gcc.gnu.org |sh do you need ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29760