From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [testsuite] Fix running in-src-dir in the same directory twice
Date: Fri, 29 Aug 2014 13:13:00 -0000 [thread overview]
Message-ID: <20140829131326.GA19760@host2.jankratochvil.net> (raw)
In-Reply-To: <21503.42231.813828.804626@ruffy2.mtv.corp.google.com>
On Thu, 28 Aug 2014 23:53:59 +0200, Doug Evans wrote:
> Tests can prematurely terminate for various unanticipatable reasons.
> Can this be solved by making sure any possibly hazardous left
> over files are cleaned up at start?
I think it would be best to modify the testcase so that the '. -> symlink'
is made in a special subdirectory so that the *.exp files loop cannot occur
even if the symlink is left there.
Besides that I think it is primarily a dejagnu/runtest bug but I did not file
it.
Jan
next prev parent reply other threads:[~2014-08-29 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 21:10 Jan Kratochvil
2014-08-29 12:38 ` Doug Evans
2014-08-29 12:49 ` Jan Kratochvil
2014-08-29 13:13 ` Jan Kratochvil [this message]
2014-08-29 21:10 ` [patchv2] " 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=20140829131326.GA19760@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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