Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Another board file for remote host
Date: Fri, 29 Aug 2014 01:55:00 -0000	[thread overview]
Message-ID: <8761hcf4g8.fsf@codesourcery.com> (raw)
In-Reply-To: <20140828211728.GA5062@host2.jankratochvil.net> (Jan Kratochvil's	message of "Thu, 28 Aug 2014 23:17:28 +0200")

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.
IIRC, when Tom worked on parallel testing, we think it should be fine to
leave remote host testing serialized.

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

-- 
Yao (齐尧)


  reply	other threads:[~2014-08-29  1:55 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 [this message]
2014-08-29 12:30     ` Jan Kratochvil
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=8761hcf4g8.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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