From: Doug Evans <dje@google.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Source files are deleted in in-tree build/test
Date: Mon, 29 Sep 2014 04:06:00 -0000 [thread overview]
Message-ID: <CADPb22QwKQGCf89EXAGodT0fbVYVDOi=OQNScxn5-iV3adAYRw@mail.gmail.com> (raw)
In-Reply-To: <877g121o4c.fsf@codesourcery.com>
On Wed, Sep 17, 2014 at 4:29 AM, Yao Qi <yao@codesourcery.com> wrote:
>
> Hi,
> If we do in-tree build and run tests sequentially,
>
> $ make check RUNTESTFLAGS='--directory=gdb.dwarf'
> $ make check RUNTESTFLAGS='--directory=gdb.python'
>
> we can see some source files are deleted after tests,
> [...]
> Alternatively, we don't have to remote these files
> copied to host. We discussed this there
> <https://sourceware.org/ml/gdb-patches/2014-08/msg00269.html> without
> any conclusions. Now, I am inclined to not removing files on host, as
> justified by this problem. What do you think?
Fine by me.
next prev parent reply other threads:[~2014-09-29 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 11:33 Yao Qi
2014-09-29 4:06 ` Doug Evans [this message]
2014-09-29 14:01 ` [PATCH 1/2] Don't remove files copied to host Yao Qi
2014-09-29 14:01 ` [PATCH 2/2] Rename py-objfile-script-gdb.py.in to py-objfile-script-gdb.py Yao Qi
2014-10-20 5:45 ` [PATCH 1/2] Don't remove files copied to host 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='CADPb22QwKQGCf89EXAGodT0fbVYVDOi=OQNScxn5-iV3adAYRw@mail.gmail.com' \
--to=dje@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).