From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 6I2NOKCQPmQTfi8AWB0awg (envelope-from ) for ; Tue, 18 Apr 2023 08:44:16 -0400 Received: by simark.ca (Postfix, from userid 112) id E52771E221; Tue, 18 Apr 2023 08:44:16 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=ex8gCIIx; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 8ED0A1E0D5 for ; Tue, 18 Apr 2023 08:44:16 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id D3D733858C2D for ; Tue, 18 Apr 2023 12:44:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D3D733858C2D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681821855; bh=5BkEqHmxbTsZzx8+sbNiY1Py/jXUlI3geEgzroasdXs=; h=Date:Subject:To:References:Cc:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=ex8gCIIxDnGM83qrBQoHTTO3YY1jGC2429dHW79DG0daYwfhuAsnPr8ueM+dn6oux F54jXNLn8DvRMueoAhFWejdseOtJEJr8g+ul6KZNq6hi6d5wiAPdiQFeEg1YQvPOdO 5e4TFfR9J0jEsURRjR/6XG0hoe9mLt28tDBR1wl0= Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by sourceware.org (Postfix) with ESMTPS id 23B153858425 for ; Tue, 18 Apr 2023 12:43:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 23B153858425 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 0882221A8D; Tue, 18 Apr 2023 12:43:56 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id E2C2E139EC; Tue, 18 Apr 2023 12:43:55 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 96M1NouQPmRZHAAAMHmgww (envelope-from ); Tue, 18 Apr 2023 12:43:55 +0000 Message-ID: <97c65614-e1a5-a9cb-b5a3-36020e8ed259@suse.de> Date: Tue, 18 Apr 2023 14:43:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: [PATCH 1/1] [gdb/contrib] Add make-check-all.sh Content-Language: en-US To: gdb-patches@sourceware.org, Simon Marchi References: <20230403150957.28921-1-tdevries@suse.de> <20230403150957.28921-2-tdevries@suse.de> <87wn2rc22u.fsf@redhat.com> Cc: Andrew Burgess In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: , From: Tom de Vries via Gdb-patches Reply-To: Tom de Vries Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 4/5/23 11:01, Tom de Vries via Gdb-patches wrote: > On 4/4/23 13:35, Andrew Burgess wrote: >> Tom de Vries via Gdb-patches writes: >> >>> Add script gdb/contrib/make-check-all.sh, that's intended to function >>> as a >>> drop-in replacement of make check, but excercising all host/target >>> boards in >>> gdb/testsuite/boards. >>> >>> Shell-checked and tested on x86_64-linux. >> >> Hi Tom, >> >> Thanks for putting this together, I think this could be really useful. >> > > That's great to hear :) > >> I'm not a fan of the way you've split the patch description into email >> 0/1 and not included it with this commit.  I think there's lots of >> useful information in there, and I'd much rather have the whole >> description included in the commit message -- it's much easier to find >> then rather than having to hunt on the mailing list in the future. >> > > Ack, I've reworked this into a patch rather than patch series. > >>> --- >>>   gdb/contrib/make-check-all.sh | 255 ++++++++++++++++++++++++++++++++++ >>>   1 file changed, 255 insertions(+) >>>   create mode 100755 gdb/contrib/make-check-all.sh >>> >>> diff --git a/gdb/contrib/make-check-all.sh >>> b/gdb/contrib/make-check-all.sh >>> new file mode 100755 >>> index 00000000000..1befe418b81 >>> --- /dev/null >>> +++ b/gdb/contrib/make-check-all.sh >>> @@ -0,0 +1,255 @@ >>> +#!/bin/bash >>> + >>> +# Copyright (C) 2023 Free Software Foundation, Inc. >>> +# This program is free software; you can redistribute it and/or modify >>> +# it under the terms of the GNU General Public License as published by >>> +# the Free Software Foundation; either version 3 of the License, or >>> +# (at your option) any later version. >>> +# >>> +# This program is distributed in the hope that it will be useful, >>> +# but WITHOUT ANY WARRANTY; without even the implied warranty of >>> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the >>> +# GNU General Public License for more details. >>> +# >>> +# You should have received a copy of the GNU General Public License >>> +# along with this program.  If not, see . >>> + >>> +# Run make check with all boards from gdb/testsuite/boards. >> >> I think you need some kind of usage test here too.  Imagine a new >> developer finds this file and looks inside.  Ideally, I think they >> should know how to use it, and what it will do for them without having >> to read any of the actual script content. >> > > Added. > >> On implementation, I wonder if it would be useful to provide a mechanism >> by which the gdb.sum and gdb.log files for each test run could be >> preserved? >> > > Done, I've renamed --keep to --keep-tmp, and added this new > functionality under --keep. > > I've also added "set -e" to make sure ^C aborts the script rather than > just one make check invocation, and moved the tmpdir removal to a > cleanup function that's executed on exit, to make sure ^C doesn't leave > tmpdirs behind. > I'd like to commit this at the end of the week, if there are no further review comments. Simon, I remember discussing something similar with you a few years ago ( https://sourceware.org/pipermail/gdb-patches/2020-May/169003.html ), so I wondered if you have any comments on this approach. Thanks, - Tom