From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24220 invoked by alias); 27 Sep 2003 15:46:28 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24213 invoked from network); 27 Sep 2003 15:46:27 -0000 Received: from unknown (HELO localhost.redhat.com) (65.49.0.121) by sources.redhat.com with SMTP; 27 Sep 2003 15:46:27 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 4B8262B8D; Sat, 27 Sep 2003 10:24:16 -0400 (EDT) Message-ID: <3F759D90.8050203@redhat.com> Date: Sat, 27 Sep 2003 15:46:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Carlton Cc: dejagnu@gnu.org, gdb@sources.redhat.com, Fernando Nasser Subject: Re: Print KFAIL's in dejagnu summary? References: <3F7361BB.1000706@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-09/txt/msg00337.txt.bz2 > On Thu, 25 Sep 2003 17:44:27 -0400, Andrew Cagney said: > > >> At present KFAILs are supressed from the summary output (the stuff >> on the terminal from "make check"). I'd like to change this so that >> KFAILs, just like FAILs, are included in the summary. A KFAIL, just >> like a FAIL, indicates a bug in the system under test, and hence >> should be included in the summary. > > > I have a mild preference for the current behavior. Mostly I use the > summary output to get a feel for whether or not a change of mine has > obviously gone wrong; the noisier the summary output is, the harder it > is to use it this way. Of course, I always search the entire gdb.sum > for regressions, just to make sure, so it won't make a big practical > difference to me one way or another. The numbers at the bottom should tell you that: - no errors - no unexpected passes - no unknown failures. unfortunatly, the only truely robust way is to compare the .sum files. Andrew