[Android] Add support for layering device-located test files.

[Android] Add support for layering device-located test files.

We need to split test files copied to devices by layers to avoid
content or webview tests using files from chrome layer directory.

To avoid modifying existing tests, test files from all layers are
merged into a single directory on a device.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=156302

[bulach, 2012-09-11 10:35:06]

http://codereview.chromium.org/10933011/diff/1/build/android/pylib/run_java_t...
File build/android/pylib/run_java_tests.py (right):

http://codereview.chromium.org/10933011/diff/1/build/android/pylib/run_java_t...
build/android/pylib/run_java_tests.py:177: cmd_helper.RunCmd(['cp', '-r',
src_dir, temp_dir])
hmm.. how many tests do we have versus how many files this would copy over time?
:)
it'd probably be simpler to fix the (few) tests, and then from now on we'd read
from the right place?

I mean, there could be conflicts in files with the same name but different data,
plus we'd be doing this copy every time we're running the tests, etc.. I don't
think we have that many tests that would need fixing, and then we can avoid any
future problem.. :) what do you think?

[mnaganov (inactive), 2012-09-11 16:45:03]

https://chromiumcodereview.appspot.com/10933011/diff/1/build/android/pylib/ru...
File build/android/pylib/run_java_tests.py (right):

https://chromiumcodereview.appspot.com/10933011/diff/1/build/android/pylib/ru...
build/android/pylib/run_java_tests.py:177: cmd_helper.RunCmd(['cp', '-r',
src_dir, temp_dir])
On 2012/09/11 10:35:06, bulach wrote:
> hmm.. how many tests do we have versus how many files this would copy over
time?
> :)
> it'd probably be simpler to fix the (few) tests, and then from now on we'd
read
> from the right place?
> 
> I mean, there could be conflicts in files with the same name but different
data,
> plus we'd be doing this copy every time we're running the tests, etc.. I don't
> think we have that many tests that would need fixing, and then we can avoid
any
> future problem.. :) what do you think?

OK, changed to avoid merging -- looks simpler. This requires a bit of downstream
changes, also sending them to you.

[bulach, 2012-09-12 15:08:40]

lgtm, many thanks!