From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove symlinks created in argv0-symlink.exp and general cleanup
Date: Mon, 03 Aug 2015 14:23:00 -0000 [thread overview]
Message-ID: <55BF7962.3060106@redhat.com> (raw)
In-Reply-To: <1438287227-11303-1-git-send-email-simon.marchi@ericsson.com>
On 07/30/2015 09:13 PM, Simon Marchi wrote:
> When running argv0-symlink.exp, symlinks are left in the test output
> directory. One of them is a recursive symlink. This causes the same tests
> to be found multiple times and disturbs subsequent test runs.
>
> To witness it simply, just run
>
> $ make check RUNTESTFLAGS="argv0-symlink.exp"
>
> twice in a row. The second run will find and run argv0-symlink.exp
> multiple times because of the recursive symlink left by the first run. Note
> that this only happens when building in tree. The simple fix is to
> remove the links when we are done.
>
> At the same time, I did a general cleanup of the test:
>
> - Add and use a create_link proc.
> - Bail out early if target does not support argv[0].
What's the rationale for that? It seems that'd skip the
tests that ensure that "info inferiors" shows the $filelink; those
aren't currently guarded by $has_argv. AFAICS, that was done
on purpose. See:
git show 673dc4a0
git show 673dc4a0:gdb/testsuite/gdb.base/argv0-symlink.exp
> - Of course, remove created symlinks before returning.
I think you should leave them, actually. That's a general direction
we've been following -- leaving build/test artifacts in place in case
the test fails and we need to debug what happened.
So instead what we do is remove any leftover from a previous run
that could interfere, when we start a new run. (I think the patch
is already doing that too.)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-08-03 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 20:13 Simon Marchi
2015-08-03 14:23 ` Pedro Alves [this message]
2015-08-03 15:16 ` Simon Marchi
2015-08-03 16:34 ` Pedro Alves
2015-08-03 16:38 ` Pedro Alves
2015-08-03 18:10 ` Simon Marchi
2015-08-03 18:42 ` Pedro Alves
2015-08-04 16:11 ` Sergio Durigan Junior
2015-08-04 17:21 ` Joel Brobecker
2015-08-11 17:36 ` Doug Evans
2015-08-11 19:58 ` Joel Brobecker
2015-08-11 20:43 ` Doug Evans
2015-08-11 23:02 ` Joel Brobecker
2015-08-12 9:30 ` Pedro Alves
2015-08-12 16:40 ` Sergio Durigan Junior
2015-08-12 17:22 ` Joel Brobecker
2015-08-12 17:38 ` Doug Evans
2015-08-12 18:43 ` Joel Brobecker
2015-08-12 18:50 ` Doug Evans
2015-08-12 19:41 ` Joel Brobecker
2015-08-12 20:23 ` Doug Evans
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=55BF7962.3060106@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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