Fix timeout for mus_browsertests/mash_browsertests

Fix timeout for mus_browsertests/mash_browsertests

Two problems here:
. timeout is in seconds, not minutes.
. hard_timeout needs to be inside the swarming block, otherwise it's
  not used at all.

BUG=none
TEST=none
R=rockot@chromium.org
TBR=rockot@chromium.org

Review-Url: https://codereview.chromium.org/2856183002
Cr-Commit-Position: refs/heads/master@{#469231}
Committed: https://chromium.googlesource.com/chromium/src/+/ffc595bc81b4a23043061b5b34c66c8a4ab06612

[sky, 2017-05-03 15:40:58]

Description was changed from

==========
Fix timeout for mus_browsertests/mash_browsertests

Two problems here:
. timeout is in seconds, not minutes.
. hard_timeout needs to be inside the swarming block, otherwise it's
  not used at all.

BUG=none
TEST=none
R=rockot@chromium.org
==========

to

==========
Fix timeout for mus_browsertests/mash_browsertests

Two problems here:
. timeout is in seconds, not minutes.
. hard_timeout needs to be inside the swarming block, otherwise it's
  not used at all.

BUG=none
TEST=none
R=rockot@chromium.org
TBR=rockot@chromium.org
==========

[sky, 2017-05-03 15:41:18]

I'm TBRing this given we spoke about it in the office.

[sky, 2017-05-03 15:41:21]

The CQ bit was checked by sky@chromium.org

[commit-bot: I haz the power, 2017-05-03 15:41:59]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-03 16:35:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-03 16:35:07]

Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Ken Rockot(use gerrit already), 2017-05-03 17:43:24]

lgtm

https://codereview.chromium.org/2856183002/diff/1/testing/buildbot/chromium.c...
File testing/buildbot/chromium.chromiumos.json (right):

https://codereview.chromium.org/2856183002/diff/1/testing/buildbot/chromium.c...
testing/buildbot/chromium.chromiumos.json:256: "hard_timeout": 90
900? :)

Though if we think we can get mash_browser_tests completing in 90 seconds I'm
all for it!

[Ken Rockot(use gerrit already), 2017-05-03 17:43:53]

On 2017/05/03 at 17:43:24, Ken Rockot wrote:
> lgtm
> 
>
https://codereview.chromium.org/2856183002/diff/1/testing/buildbot/chromium.c...
> File testing/buildbot/chromium.chromiumos.json (right):
> 
>
https://codereview.chromium.org/2856183002/diff/1/testing/buildbot/chromium.c...
> testing/buildbot/chromium.chromiumos.json:256: "hard_timeout": 90
> 900? :)
> 
> Though if we think we can get mash_browser_tests completing in 90 seconds I'm
all for it!

Also I guess it's worth pointing out that the timeout is clearly working, as the
tests indeed failed with a 90 second timeout!

[sky, 2017-05-04 00:13:30]

The CQ bit was checked by sky@chromium.org

[sky, 2017-05-04 00:13:31]

The patchset sent to the CQ was uploaded after l-g-t-m from rockot@chromium.org
Link to the patchset: https://codereview.chromium.org/2856183002/#ps20001
(title: "900")

[commit-bot: I haz the power, 2017-05-04 00:13:54]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-04 01:25:11]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1493856810926750,
"parent_rev": "7fb6670abe4d5f8d6caa26f39bf147c3844a3ec8", "commit_rev":
"ffc595bc81b4a23043061b5b34c66c8a4ab06612"}

[commit-bot: I haz the power, 2017-05-04 01:25:26]

Description was changed from

==========
Fix timeout for mus_browsertests/mash_browsertests

Two problems here:
. timeout is in seconds, not minutes.
. hard_timeout needs to be inside the swarming block, otherwise it's
  not used at all.

BUG=none
TEST=none
R=rockot@chromium.org
TBR=rockot@chromium.org
==========

to

==========
Fix timeout for mus_browsertests/mash_browsertests

Two problems here:
. timeout is in seconds, not minutes.
. hard_timeout needs to be inside the swarming block, otherwise it's
  not used at all.

BUG=none
TEST=none
R=rockot@chromium.org
TBR=rockot@chromium.org

Review-Url: https://codereview.chromium.org/2856183002
Cr-Commit-Position: refs/heads/master@{#469231}
Committed:
https://chromium.googlesource.com/chromium/src/+/ffc595bc81b4a23043061b5b34c6...
==========

[commit-bot: I haz the power, 2017-05-04 01:25:31]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/ffc595bc81b4a23043061b5b34c6...

[sky, 2017-05-04 02:18:19]

On 2017/05/03 17:43:24, Ken Rockot wrote:
> lgtm
> 
>
https://codereview.chromium.org/2856183002/diff/1/testing/buildbot/chromium.c...
> File testing/buildbot/chromium.chromiumos.json (right):
> 
>
https://codereview.chromium.org/2856183002/diff/1/testing/buildbot/chromium.c...
> testing/buildbot/chromium.chromiumos.json:256: "hard_timeout": 90
> 900? :)
> 
> Though if we think we can get mash_browser_tests completing in 90 seconds I'm
> all for it!

Fixed!