Re: [PATCH 0/3] Keep track of files copied to host and target

[Yao Qi <yao at codesourcery dot com>]

On 08/16/2014 08:38 AM, Doug Evans wrote:
> We could instead have a convention that we just don't bother to clean
> up files downloaded to remote hosts.

This patch https://sourceware.org/ml/gdb-patches/2009-11/msg00264.html
is the first one downloading files to remote host and deleting them when
test is finished.  After that, people just follow this convention, and
add test cases in this way.  Unfortunately, no technical reason is
mentioned in the patch about why we have to delete files on remote host.


> Sure, but I'd like to get a better understanding of the technical
> reasons for doing so.

I don't know any technical reasons either.  What I can tell from the
patch above is that "the first person did so, and the rest follow the
way he did".

Looks this patch set review is stalled.  You worried about the direction
or convention that we only delete part of files copied to host, but I
don't know the answer of your questions, which are about the convention
rather than patches.  I don't think my patch set makes it worse or
better.  It still make the effect of running testsuite unchanged, in
terms of files left on target and host.

At the same time, fails in gdb.python on remote host are still there
because patch 3/3 is pending.  My goal of this patch series is to fix
these fails, but I don't know how to move forward now.

-- 
Yao (éå)