From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15936 invoked by alias); 5 Aug 2002 22:55:35 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 15929 invoked from network); 5 Aug 2002 22:55:33 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 5 Aug 2002 22:55:33 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g75Mgfl26550 for ; Mon, 5 Aug 2002 18:42:41 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g75MtUu07525; Mon, 5 Aug 2002 18:55:31 -0400 Received: from romulus.sfbay.redhat.com (IDENT:9Qt7WPxwzRo8c/RXkKeO9OR0R+Tf1Xny@romulus.sfbay.redhat.com [172.16.27.251]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g75MtTB26383; Mon, 5 Aug 2002 15:55:30 -0700 Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g75MtQ626570; Mon, 5 Aug 2002 15:55:26 -0700 Date: Mon, 05 Aug 2002 15:55:00 -0000 From: Kevin Buettner Message-Id: <1020805225525.ZM26569@localhost.localdomain> In-Reply-To: Andrew Cagney "[rfa/testsuite] One pass/fail per expect list" (Jun 14, 3:46pm) References: <3D0A4801.8030001@cygnus.com> To: Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: [rfa/testsuite] One pass/fail per expect list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00102.txt.bz2 On Jun 14, 3:46pm, Andrew Cagney wrote: > The attached tweaks gdb_expect_list{} so that it only prints one pass / > fail / ... message for the testcase. > > What are peoples thoughts on this change and if positive, is the patch ok? Now that it's in and I've had a chance to use it, the only part that I don't like is: > - unresolved "${test}, pattern ${index} + sentinel" > + # unresolved "${test}, pattern ${index} + sentinel" I found it useful to see the (potentially long list of) UNRESOLVED messages after the FAIL so that I knew how many other parts of the test hadn't been checked. Kevin