From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-6884-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 3809 invoked by alias); 25 Nov 2001 17:41:50 -0000
Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 3788 invoked from network); 25 Nov 2001 17:41:50 -0000
Received: from unknown (HELO handhelds.org) (204.123.13.90)
  by sourceware.cygnus.com with SMTP; 25 Nov 2001 17:41:50 -0000
Received: from shadowfax.middleearth (IDENT:root@localhost [127.0.0.1])
	by handhelds.org (8.9.3/8.9.3) with SMTP id JAA32617;
	Sun, 25 Nov 2001 09:41:47 -0800
From: George France <france@handhelds.org>
To: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: exit status of 'make check'
Date: Mon, 12 Nov 2001 15:02:00 -0000
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="us-ascii"
References: <200111212321.RAA09463@duracef.shout.net> <01112208082500.16429@shadowfax.middleearth> <20011125015054.A31912@nevyn.them.org>
In-Reply-To: <20011125015054.A31912@nevyn.them.org>
Cc: clp@iol.unh.edu
MIME-Version: 1.0
Message-Id: <01112512374200.05740@shadowfax.middleearth>
Content-Transfer-Encoding: 8bit
X-SW-Source: 2001-11/txt/msg00131.txt.bz2

> That pretty much means that it did.  You can grep for ^FAIL: to see how
> many there are.  I'm hoping to see the GDB testsuite pass entirely for
> some target, someday...

Greetings,

Even if all the testsuites have a FAILed status, 'make check' should not 
return a non-zero exit code unless there is a failure in the 'make check' 
programs. The programs that comprise 'make check' should succeed.  

For example, if the "gdb.base/annota1.exp: breakpoint info" testsuite fails, 
it is a failure of that testsuite, not 'make check'.  Not finding 'runtest' 
would be an example of a failure in 'make check', that should return a 
non-zero exit code.

Currently 'make check' always returns a non-zero exit code indicating the 
testsuite results are unreliable due to a failure in 'make check'. 

I hope this makes things clearer.

Best Regards,


--George