Re: [PATCH] Support 'make check-parallel' in gdb's build dir

[Pedro Alves <palves@redhat.com>]

On 02/11/2016 04:44 PM, Simon Marchi wrote:
> 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?

Host in the Dejagnu terminology, as in [is_remote host].

> 
> 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?

Right.

> 
> 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.

Thanks,
Pedro Alves