Android: Avoid multiple data file pushes for unittests

Android: Avoid multiple data file pushes for unittests

This also fixes failures in content_unittests and components_unittests when they are run separately.

BUG=


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

[frankf, 2013-04-08 19:19:37]

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
File build/android/pylib/gtest/test_runner.py (left):

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
build/android/pylib/gtest/test_runner.py:33: if test_suite_basename in
['base_unittests', 'sql_unittests', 'unit_tests']:
sql_unittests don't have any deps?

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
File build/android/pylib/gtest/test_runner.py (right):

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
build/android/pylib/gtest/test_runner.py:70: 'net/data/ssl/certificates',
I'm assuming trailing slash is optional.

[nilesh, 2013-04-08 23:50:57]

I will rebase with https://codereview.chromium.org/13467035/ and update the CL.

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
File build/android/pylib/gtest/test_runner.py (left):

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
build/android/pylib/gtest/test_runner.py:33: if test_suite_basename in
['base_unittests', 'sql_unittests', 'unit_tests']:
On 2013/04/08 19:19:37, frankf wrote:
> sql_unittests don't have any deps?

No, no files are needed for sql_unittests.

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
File build/android/pylib/gtest/test_runner.py (right):

https://codereview.chromium.org/13637010/diff/1/build/android/pylib/gtest/tes...
build/android/pylib/gtest/test_runner.py:70: 'net/data/ssl/certificates',
On 2013/04/08 19:19:37, frankf wrote:
> I'm assuming trailing slash is optional.

yes.

[nilesh, 2013-04-09 00:08:07]

Rebased and created a section for components_unittests. Please take another
look.

[frankf, 2013-04-09 00:17:39]

So this needs to be tested by clobbering the device and using -c to clean up
after each suite. Otherwise, you might mask some dependencies.

lgtm.

On 2013/04/09 00:08:07, nilesh wrote:
> Rebased and created a section for components_unittests. Please take another
> look.

[nilesh, 2013-04-09 00:21:41]

On 2013/04/09 00:17:39, frankf wrote:
> So this needs to be tested by clobbering the device and using -c to clean up
> after each suite. Otherwise, you might mask some dependencies.

I have tested this for the test suites I am modifying in this CL

[commit-bot: I haz the power, 2013-04-09 00:36:31]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nileshagrawal@chromium.org/13637010/6001

[commit-bot: I haz the power, 2013-04-09 01:02:42]

Step "update" is always a major failure.
Look at the try server FAQ for more details.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[commit-bot: I haz the power, 2013-04-09 02:39:51]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nileshagrawal@chromium.org/13637010/6001

[commit-bot: I haz the power, 2013-04-09 02:42:34]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nileshagrawal@chromium.org/13637010/6001

[commit-bot: I haz the power, 2013-04-09 05:44:51]

Retried try job too often on linux_chromeos for step(s) browser_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

[commit-bot: I haz the power, 2013-04-09 06:33:37]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nileshagrawal@chromium.org/13637010/6001

[commit-bot: I haz the power, 2013-04-09 08:46:29]

Change committed as 193039