Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>, Doug Evans <xdje42@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Run tests in sub dir of testsuite/
Date: Fri, 12 Dec 2014 11:35:00 -0000	[thread overview]
Message-ID: <548AD312.6010707@redhat.com> (raw)
In-Reply-To: <54890CDE.8050405@codesourcery.com>

On 12/11/2014 03:17 AM, Yao Qi wrote:
> On 12/11/2014 11:05 AM, Doug Evans wrote:
>> Is there intended to be a followup patch to remove
>> all the makefiles in testsuite/ except testsuite/Makefile.in?
>>
>> [I realize this patch is just RFC.
>> I just want to understand where this is headed.]
> 
> Yes, that is what I want to do in next step.
> 
>>
>> btw, while it might be cleaner to move gdb.log,gdb.sum into
>> the subdirs, it's not necessary.
>> I can update my build scripts, but if we're going
>> to be affecting a lot of build scripts then I'd
>> reconsider.
> 
> I am fine to leave gdb.log and gdb.sum in testsuite/.  The reason I move
> them into testsuite/$OUTPUTSDIR/ is to make $OUTPUTSDIR self-contained.
>  Either way is fine to me, and I don't have a strong
> opinion on this.

I tend to think it's better to leave them be if there's no
real good reason to move them.

Note that "make clean" doesn't delete gdb.sum/gdb.log,
"make distclean" does.  If "make clean" is just going to be "rm -f $subdirs",
then to preserve that it seems simplest to keep gdb.sum and gdb.log out
of the subdirs.

(nit, on "sequential-tests"/"parallel-tests" -- it's the run, not the
tests that are sequential or parallel.  I'd suggest dropping
"-tests" from the dir names or use "-run", to avoid potential confusion.)

Thanks,
Pedro Alves


  reply	other threads:[~2014-12-12 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  2:54 Yao Qi
2014-12-11  3:06 ` Doug Evans
2014-12-11  3:18   ` Yao Qi
2014-12-12 11:35     ` Pedro Alves [this message]
2014-12-14  6:12       ` Yao Qi
2014-12-25  2:46 ` Yao Qi
2015-01-11 12:36   ` Yao Qi

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=548AD312.6010707@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.com \
    --cc=yao@codesourcery.com \
    /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