[Android] Extend setup timeout for content_browsertests.

[Android] Extend setup timeout for content_browsertests.

content_browsertests were timing out on the Android FYI bots since it
took more than 7 minutes to push the test files to the device. This
extends the timeout to 20 minutes, as a stopgap until we can reduce
the number of files that need to be pushed.

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

[nilesh, 2013-04-05 21:23:54]

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
File build/android/pylib/browsertests/dispatch.py (right):

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
build/android/pylib/browsertests/dispatch.py:71: test_timeout=None)
we also need more than 7 mins to run these, specially for bots with only 1
device.

[newt (away), 2013-04-05 21:41:24]

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
File build/android/pylib/browsertests/dispatch.py (right):

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
build/android/pylib/browsertests/dispatch.py:71: test_timeout=None)
On 2013/04/05 21:23:54, nilesh wrote:
> we also need more than 7 mins to run these, specially for bots with only 1
> device. 

test_timeout=None means they can't time out. see:
build/android/pylib/utils/watchdog_timer.py

[craigdh, 2013-04-05 22:00:02]

lgtm.

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
File build/android/pylib/browsertests/dispatch.py (right):

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
build/android/pylib/browsertests/dispatch.py:71: test_timeout=None)
On 2013/04/05 21:41:25, newt wrote:
> On 2013/04/05 21:23:54, nilesh wrote:
> > we also need more than 7 mins to run these, specially for bots with only 1
> > device. 
> 
> test_timeout=None means they can't time out. see:
> build/android/pylib/utils/watchdog_timer.py

Both content_browsertests and gtests have timeouts disabled during the tests
because of how they use a gtest filter to run multiple tests together.
Instrumentation tests reset the timeout after each test.

[nilesh, 2013-04-05 22:05:23]

On 2013/04/05 22:00:02, craigdh wrote:
> lgtm.
> 
>
https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
> File build/android/pylib/browsertests/dispatch.py (right):
> 
>
https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
> build/android/pylib/browsertests/dispatch.py:71: test_timeout=None)
> On 2013/04/05 21:41:25, newt wrote:
> > On 2013/04/05 21:23:54, nilesh wrote:
> > > we also need more than 7 mins to run these, specially for bots with only 1
> > > device. 
> > 
> > test_timeout=None means they can't time out. see:
> > build/android/pylib/utils/watchdog_timer.py
> 
> Both content_browsertests and gtests have timeouts disabled during the tests
> because of how they use a gtest filter to run multiple tests together.

content_browsertests use gtest filter to run one test at a time. It is rum more
like the instrumentation tests.
> Instrumentation tests reset the timeout after each test.

[nilesh, 2013-04-05 22:10:12]

lgtm

[craigdh, 2013-04-05 22:18:37]

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
File build/android/pylib/browsertests/dispatch.py (right):

https://codereview.chromium.org/13674021/diff/1/build/android/pylib/browserte...
build/android/pylib/browsertests/dispatch.py:71: test_timeout=None)
On 2013/04/05 22:00:03, craigdh wrote:
> On 2013/04/05 21:41:25, newt wrote:
> > On 2013/04/05 21:23:54, nilesh wrote:
> > > we also need more than 7 mins to run these, specially for bots with only 1
> > > device. 
> > 
> > test_timeout=None means they can't time out. see:
> > build/android/pylib/utils/watchdog_timer.py
> 
> Both content_browsertests and gtests have timeouts disabled during the tests
> because of how they use a gtest filter to run multiple tests together.
> Instrumentation tests reset the timeout after each test.

In that case please take out test_timeout=None, I assume none of the individual
tests take more than seven minutes?

[commit-bot: I haz the power, 2013-04-05 23:10:09]

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

[commit-bot: I haz the power, 2013-04-06 01:10:42]

Change committed as 192682