From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alt-proxy28.mail.unifiedlayer.com (alt-proxy28.mail.unifiedlayer.com [74.220.216.123]) by sourceware.org (Postfix) with ESMTPS id 678AA3857BBD for ; Fri, 15 Jul 2022 16:34:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 678AA3857BBD Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tromey.com Received: from cmgw15.mail.unifiedlayer.com (unknown [10.0.90.130]) by progateway1.mail.pro1.eigbox.com (Postfix) with ESMTP id 80CF81003FCF1 for ; Fri, 15 Jul 2022 16:34:05 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id COGSo5KLqjIMdCOGTojHcH; Fri, 15 Jul 2022 16:34:05 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=ebP4w5IH c=1 sm=1 tr=0 ts=62d196fd a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=RgO8CyIxsXoA:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=Adv5dce7Srjay4E0eToA:9 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=1xo4XPkzK8X5w8YTcI+CADP7Zf0ITczfvm9zPDnIBGk=; b=GZ8EHGDp0A2FzmGm3yMW6oUlFo r498eptHVMtpdb9i/L2ofpPuYj2LfUj5jhYgqXM2YwF6eZC+Nafh7gufGYmMr87QFDwbxy4xe07x/ lZwRShIqKUOb6fdiZgGrvq7o6; Received: from 71-211-185-228.hlrn.qwest.net ([71.211.185.228]:56090 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oCOGS-001y8H-KC; Fri, 15 Jul 2022 10:34:04 -0600 From: Tom Tromey To: Tiezhu Yang Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] gdb: Remove duplicate "gdb Summary" in the test output References: <1656127865-10255-1-git-send-email-yangtiezhu@loongson.cn> X-Attribution: Tom Date: Fri, 15 Jul 2022 10:34:03 -0600 In-Reply-To: <1656127865-10255-1-git-send-email-yangtiezhu@loongson.cn> (Tiezhu Yang's message of "Sat, 25 Jun 2022 11:31:05 +0800") Message-ID: <87v8rypc78.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 71.211.185.228 X-Source-L: No X-Exim-ID: 1oCOGS-001y8H-KC X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 71-211-185-228.hlrn.qwest.net (murgatroyd) [71.211.185.228]:56090 X-Source-Auth: tom+tromey.com X-Email-Count: 14 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3023.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2022 16:34:17 -0000 >>>>> Tiezhu Yang writes: > There exists duplicate "gdb Summary" in the test output, just modify > gdb/testsuite/Makefile.in to remove the redundant info. > Here is an example, when execute the following command: > make check-gdb TESTS="gdb.base/a2-run.exp" I think what's happening here is that the "Summary" line is added for the benefit of parallel "make check". However, in your case, you're only running a single test. But, if you run many tests, I think the output won't look redundant. So, I tend to think it should just remain the way it is. Tom