From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12627 invoked by alias); 26 Nov 2001 05:11:04 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12605 invoked from network); 26 Nov 2001 05:11:01 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sourceware.cygnus.com with SMTP; 26 Nov 2001 05:11:01 -0000 Received: (from mec@localhost) by duracef.shout.net (8.8.7/8.8.7) id XAA27776; Sun, 25 Nov 2001 23:10:49 -0600 Date: Tue, 13 Nov 2001 10:34:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200111260510.XAA27776@duracef.shout.net> To: drow@mvista.com, france@handhelds.org Subject: Re: exit status of 'make check' Cc: clp@iol.unh.edu, gdb@sources.redhat.com X-SW-Source: 2001-11/txt/msg00143.txt.bz2 I agree with Daniel here, but from a different point of view. It would be nice if the exit status was, for example: 0 no results are ERROR, WARNING, or FAIL 1 no results are ERROR or WARNING; some results are FAIL 2 some results are ERROR or WARNING 3 the test harness did not run well enough to generate results (e.g. runtest not found). (or something like that) To achieve this result, someone would have to: design a set of exit statuses, build consensus for it among several user communities, and submit patches to tools like dejagnu. That's a lot of work. For the same amount of work, one could implement other useful features in the test machinery and in the test suite itself. For instance, I would like to have ERRORs and WARNINGs reported with the test script filename in them, just like FAILs are. I do sympathize that the exit status is imprecise and that this can interfere with large-scale automation. Michael C From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Elizabeth Chastain To: drow@mvista.com, france@handhelds.org Cc: clp@iol.unh.edu, gdb@sources.redhat.com Subject: Re: exit status of 'make check' Date: Sun, 25 Nov 2001 21:11:00 -0000 Message-ID: <200111260510.XAA27776@duracef.shout.net> X-SW-Source: 2001-11/msg00250.html Message-ID: <20011125211100.7709qqaukRcFYSDa24v0TIsFtheUs49Fj6bcRsmxov4@z> I agree with Daniel here, but from a different point of view. It would be nice if the exit status was, for example: 0 no results are ERROR, WARNING, or FAIL 1 no results are ERROR or WARNING; some results are FAIL 2 some results are ERROR or WARNING 3 the test harness did not run well enough to generate results (e.g. runtest not found). (or something like that) To achieve this result, someone would have to: design a set of exit statuses, build consensus for it among several user communities, and submit patches to tools like dejagnu. That's a lot of work. For the same amount of work, one could implement other useful features in the test machinery and in the test suite itself. For instance, I would like to have ERRORs and WARNINGs reported with the test script filename in them, just like FAILs are. I do sympathize that the exit status is imprecise and that this can interfere with large-scale automation. Michael C