[Android] Add --skip-deps-push to test scripts.

[Android] Add --skip-deps-push to test scripts.
    
This bypasses syncing any deps to the device to speed up
the developer workflow.
    
BUG=243447
NOTRY=True

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

[craigdh, 2013-06-10 21:13:00]

lgtm.

[nilesh, 2013-06-10 21:45:20]

On 2013/06/10 21:13:00, craigdh wrote:
> lgtm.

LGTM

[commit-bot: I haz the power, 2013-06-10 21:47:37]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/frankf@chromium.org/16627004/1

[commit-bot: I haz the power, 2013-06-10 21:50:56]

Change committed as 205317

[nilesh, 2013-06-12 17:25:12]

https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
File build/android/pylib/base/base_test_runner.py (right):

https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
build/android/pylib/base/base_test_runner.py:93: self.PushDependencies()
This causes the apk install to be skipped as well. I dont think skipping the apk
install was intended. Was it?

[frankf, 2013-06-12 17:38:04]

On 2013/06/12 17:25:12, nilesh wrote:
>
https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
> File build/android/pylib/base/base_test_runner.py (right):
> 
>
https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
> build/android/pylib/base/base_test_runner.py:93: self.PushDependencies()
> This causes the apk install to be skipped as well. I dont think skipping the
apk
> install was intended. Was it?

Yes, this is a heavy-handed approach as we consider the apk as part of deps. If
it causes confusion/inconvinience, I can change it. WDYT?

[nilesh, 2013-06-12 17:47:05]

On 2013/06/12 17:38:04, frankf wrote:
> On 2013/06/12 17:25:12, nilesh wrote:
> >
>
https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
> > File build/android/pylib/base/base_test_runner.py (right):
> > 
> >
>
https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
> > build/android/pylib/base/base_test_runner.py:93: self.PushDependencies()
> > This causes the apk install to be skipped as well. I dont think skipping the
> apk
> > install was intended. Was it?
> 
> Yes, this is a heavy-handed approach as we consider the apk as part of deps.
If
> it causes confusion/inconvinience, I can change it. WDYT?

I think pushing the new APK is integral part of developer workflow.
Typical workflow (Add a test case, run, modify, run ..) While doing so the
developer does not want to push all the data dependencies specified for all the
tests in the APK.

What workflow did you have in mind?

[nilesh, 2013-06-12 17:48:13]

+nyquist

[craigdh, 2013-06-12 17:52:43]

On 2013/06/12 17:48:13, nilesh wrote:
> +nyquist

This also shouldn't interfere with the behavior of -I for installing the test
apk.

[frankf, 2013-06-12 18:23:29]

On 2013/06/12 17:47:05, nilesh wrote:
> On 2013/06/12 17:38:04, frankf wrote:
> > On 2013/06/12 17:25:12, nilesh wrote:
> > >
> >
>
https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
> > > File build/android/pylib/base/base_test_runner.py (right):
> > > 
> > >
> >
>
https://codereview.chromium.org/16627004/diff/1/build/android/pylib/base/base...
> > > build/android/pylib/base/base_test_runner.py:93: self.PushDependencies()
> > > This causes the apk install to be skipped as well. I dont think skipping
the
> > apk
> > > install was intended. Was it?
> > 
> > Yes, this is a heavy-handed approach as we consider the apk as part of deps.
> If
> > it causes confusion/inconvinience, I can change it. WDYT?
> 
> I think pushing the new APK is integral part of developer workflow.
> Typical workflow (Add a test case, run, modify, run ..) While doing so the
> developer does not want to push all the data dependencies specified for all
the
> tests in the APK.
> 
> What workflow did you have in mind?

Agreed: https://codereview.chromium.org/16820002/