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 19:33:00 -0000	[thread overview]
Message-ID: <56BCE209.6010901@ericsson.com> (raw)
In-Reply-To: <56BCBFE3.3080904@redhat.com>

On 16-02-11 12:07 PM, Pedro Alves wrote:
>> 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).
> 
> I think that it's because with remote host testing, unless you assume
> the build and host machines share the same file system, sources/binaries
> of all tests end up downloaded to/produced in the same remote host dir, and
> then thus tests clash if run in parallel.

Ahh it makes sense, the same thing happens with a remote target (the same procedures
in Dejagnu are used to upload the files).  So there could also be some clash when
testing with a remote target, if there are two tests with the same name, or tests that
use the same external files/libraries.  That's why I found that odd, why a remote host
in particular is dangerous, and not a remote target.

Otherwise, the README LGTM.


  reply	other threads:[~2016-02-11 19:33 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
2016-02-11 17:07   ` Pedro Alves
2016-02-11 19:33     ` Simon Marchi [this message]
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=56BCE209.6010901@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