From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Another board file for remote host
Date: Fri, 29 Aug 2014 12:30:00 -0000 [thread overview]
Message-ID: <20140829123005.GA10523@host2.jankratochvil.net> (raw)
In-Reply-To: <8761hcf4g8.fsf@codesourcery.com>
On Fri, 29 Aug 2014 03:51:51 +0200, Yao Qi wrote:
> Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> > Could it use some more unique directory name so that parallel runs of
> > testsuites from multiple independent GDB directories work?
> > And also:
> > cd gdb; make -j20 -k check//unix/-m64 check//unix/-m32
> > etc.
>
> Do we want to run testing in remote host in parallel? If RUNTESTFLAGS
> is not empty, the tests will be serialized unless FORCE_PARALLEL is set.
This is unrelated as I can run multiple testsuites at once on the same host
from unrelated GDB source-trees/build/trees.
Besides that I do use FORCE_PARALLEL:
http://git.jankratochvil.net/?p=nethome.git;a=blob;f=bin/hammock
I even run all testsuites twice at the same time - for i686 and x86_64
although I run them in different chroots so this issue would not matter.
But I could run the i686 build even on x86_64 just compiling everything
with -m32 (which I also do).
> > IIUC instead of [file tail $src] it may be better to use $src's absolute
> > directory.
>
> Do you mean, supposing $src is /home/yao/src/gdb/testsuite/gdb.base/foo.c,
> copy it to /tmp/gdb/home/yao/src/gdb/testsuite/gdb.base/foo.c?
Yes. There may be other options (such as using something PID-based etc.) but
I find the absolute pathname probably the best one.
Thanks,
Jan
next prev parent reply other threads:[~2014-08-29 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 13:35 Yao Qi
2014-08-28 14:27 ` Pedro Alves
2014-08-29 1:38 ` Yao Qi
2014-08-28 21:17 ` Jan Kratochvil
2014-08-29 1:55 ` Yao Qi
2014-08-29 12:30 ` Jan Kratochvil [this message]
2014-09-01 8:14 ` Yao Qi
2014-09-01 8:44 ` Jan Kratochvil
2014-08-29 3:28 ` Doug Evans
2014-09-02 2:52 ` Yao Qi
2014-09-02 14:53 ` Doug Evans
2014-09-04 13:22 ` Yao Qi
2014-09-15 4:46 ` Yao Qi
2014-09-15 4:55 ` Doug Evans
2014-09-15 5:35 ` Doug Evans
2014-09-15 7:59 ` 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=20140829123005.GA10523@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--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