Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Support 'make check-parallel' in gdb's build dir
Date: Thu, 11 Feb 2016 16:44:00 -0000	[thread overview]
Message-ID: <56BCBA68.6000906@ericsson.com> (raw)
In-Reply-To: <1455207502-11058-1-git-send-email-palves@redhat.com>

On 16-02-11 11:18 AM, Pedro Alves wrote:
> +check-parallel: force
> +	@if [ -f testsuite/Makefile ]; then \
> +	  rootme=`pwd`; export rootme; \
> +	  rootsrc=`cd $(srcdir); pwd`; export rootsrc; \
> +	  cd testsuite; \
> +	  $(MAKE) $(TARGET_FLAGS_TO_PASS) check-parallel; \
> +	else true; fi
> +

Thanks for making it a little bit more convenient.  I also use the check-parallel
target, it feels more natural than setting FORCE_PARALLEL.

> +Parallel testing
> +****************
> +
> +When testing natively (that is, not with a remote host), you can run

I know you just moved that text, but would you know by any chance what is
meant by "remote host" here?  Is it host in the Autoconf/Dejagnu,
terminology?

For example, if I'm building on Linux a GDB that will run on Windows to
debug some bare-metal ARM, we are in presence of a remote host which is
Windows?

I understand why you couldn't run parallel tests against a single, bare-metal
target, but I don't understand why having a remote host would limit that
(assuming you can connect multiple times simultaneously to that remote host).


  reply	other threads:[~2016-02-11 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 16:18 Pedro Alves
2016-02-11 16:44 ` Simon Marchi [this message]
2016-02-11 17:07   ` Pedro Alves
2016-02-11 19:33     ` Simon Marchi
2016-02-11 19:54       ` Pedro Alves
2016-02-11 19:58         ` Pedro Alves

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=56BCBA68.6000906@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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