Minor bug fix for run_remote_tests

Minor bug fixes for run_remote_tests

By default keep around result directories.
Also find control* named control files.

[petkov, 2010-03-18 23:44:49]

http://codereview.chromium.org/1097003/diff/2001/3001
File src/scripts/run_remote_tests.sh (right):

http://codereview.chromium.org/1097003/diff/2001/3001#newcode153
src/scripts/run_remote_tests.sh:153: ! finds=$(find ${search_path} -type f -name
control\* | \
What happens when you have multiple control files in the same test folder? Any
way to disambiguate from the command line?

[kmixter1, 2010-03-18 23:50:40]

On Thu, Mar 18, 2010 at 4:44 PM,  <petkov@chromium.org> wrote:
>
> http://codereview.chromium.org/1097003/diff/2001/3001
> File src/scripts/run_remote_tests.sh (right):
>
> http://codereview.chromium.org/1097003/diff/2001/3001#newcode153
> src/scripts/run_remote_tests.sh:153: ! finds=$(find ${search_path} -type
> f -name control\* | \
> What happens when you have multiple control files in the same test
> folder? Any way to disambiguate from the command line?

Yes, for instance you can run with an unambiguous substring, like:
run_remote_tests.sh --remote=... HWQual/control.auto

>
> http://codereview.chromium.org/1097003
>

[petkov, 2010-03-18 23:53:46]

LGTM