This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Support 'make check-parallel' in gdb's build dir
- From: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Pedro Alves <palves at redhat dot com>, <gdb-patches at sourceware dot org>
- Date: Thu, 11 Feb 2016 14:33:29 -0500
- Subject: Re: [PATCH] Support 'make check-parallel' in gdb's build dir
- Authentication-results: sourceware.org; auth=none
- References: <1455207502-11058-1-git-send-email-palves at redhat dot com> <56BCBA68 dot 6000906 at ericsson dot com> <56BCBFE3 dot 3080904 at redhat dot 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.