Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH 1/1] [gdb/contrib] Add make-check-all.sh
Date: Tue, 18 Apr 2023 14:43:56 +0200	[thread overview]
Message-ID: <97c65614-e1a5-a9cb-b5a3-36020e8ed259@suse.de> (raw)
In-Reply-To: <de208a99-edfd-a3ee-8573-6a8bf7380c99@suse.de>

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 <gdb-patches@sourceware.org> 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 <http://www.gnu.org/licenses/>.
>>> +
>>> +# 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


  reply	other threads:[~2023-04-18 12:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 15:09 [PATCH 0/1] [gdb/testsuite] Run test-case with all host/target boards Tom de Vries via Gdb-patches
2023-04-03 15:09 ` [PATCH 1/1] [gdb/contrib] Add make-check-all.sh Tom de Vries via Gdb-patches
2023-04-04 11:35   ` Andrew Burgess via Gdb-patches
2023-04-05  9:01     ` Tom de Vries via Gdb-patches
2023-04-18 12:43       ` Tom de Vries via Gdb-patches [this message]
2023-04-19 14:04         ` Simon Marchi via Gdb-patches
2023-04-20 11:43           ` Tom de Vries via Gdb-patches
2023-04-20 14:30             ` Simon Marchi via Gdb-patches
2023-04-21 15:41               ` Tom de Vries via Gdb-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=97c65614-e1a5-a9cb-b5a3-36020e8ed259@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=simark@simark.ca \
    --cc=tdevries@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox