Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] testsuite: Fix racy clashing for gdb.base{1,2}/ parallel run
Date: Mon, 13 Jul 2009 17:08:00 -0000	[thread overview]
Message-ID: <m3d484r1gi.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090712181146.GA9009@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Sun\, 12 Jul 2009 20\:11\:46 +0200")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> randomly some testcases fail now with paralell testsuite due to:

Thanks for finding and fixing this.

Jan> Some scripts have bugs so that their binary files are created in
Jan> the current directory (and not in ${subdir}).  Therefore if there
Jan> would be a change so that the current directory is always in
Jan> ${objdir} (therefore in gdb.base1) it may be better to globally
Jan> change the current directory to be in ${objdir}/${subdir}.

Yeah, consistency here would be nice.

This patch is ok.  I didn't know about prepare_for_testing -- it seems
to me that we should use this more.

Tom


  reply	other threads:[~2009-07-13 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  0:47 Jan Kratochvil
2009-07-13 17:08 ` Tom Tromey [this message]
2009-07-13 19:30   ` Jan Kratochvil

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=m3d484r1gi.fsf@fleche.redhat.com \
    --to=tromey@redhat.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