Fix timeout in rasterize_and_record_micro benchmarks

Fix timeout in rasterize_and_record_micro benchmarks

A bug was introduced when migrating to the v2 API to execute JavaScript
snippets in Telemetry. The old timeout used inconsistent defaults on
different methods, and the migration caused the timeout to drop from 90
to 60 seconds.

Rather than relying on an unseen defualt, specify an explicit timeout
on the non-obvious expression that takes a long time to evaluate.

TBR=nednguyen@google.com
BUG=691751
Review-Url: https://codereview.chromium.org/2691023003
Cr-Commit-Position: refs/heads/master@{#450325}
Committed: https://chromium.googlesource.com/chromium/src/+/58b5ae9d8d96fd72374c5ee63a7c8ad358eec9e8

[perezju, 2017-02-14 10:56:22]

perezju@chromium.org changed reviewers:
+ nednguyen@google.com

[perezju, 2017-02-14 10:56:36]

Description was changed from

==========
Fix timeout in rasterize_and_record_micro benchmarks

A bug was introduced when migrating to the v2 API to execute JavaScript
snippets in Telemetry. The old timeout used inconsistent defaults on
different methods, and the migration caused the timeout to drop from 90
to 60 seconds.

Rather than relying on an unseen defualt, specify an explicit timeout
on the non-obvious expression that takes a long time to evaluate.

BUG=691751
==========

to

==========
Fix timeout in rasterize_and_record_micro benchmarks

A bug was introduced when migrating to the v2 API to execute JavaScript
snippets in Telemetry. The old timeout used inconsistent defaults on
different methods, and the migration caused the timeout to drop from 90
to 60 seconds.

Rather than relying on an unseen defualt, specify an explicit timeout
on the non-obvious expression that takes a long time to evaluate.

TBR=nednguyen@google.com
BUG=691751
==========

[perezju, 2017-02-14 10:56:50]

TBR'ing to get benchmark unstuck.

[perezju, 2017-02-14 10:56:53]

The CQ bit was checked by perezju@chromium.org

[commit-bot: I haz the power, 2017-02-14 10:57:16]

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-02-14 11:53:54]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1487069813759220,
"parent_rev": "fb7be6dfdc206f3edd14cd46199526e22f9453c8", "commit_rev":
"58b5ae9d8d96fd72374c5ee63a7c8ad358eec9e8"}

[commit-bot: I haz the power, 2017-02-14 11:54:38]

Description was changed from

==========
Fix timeout in rasterize_and_record_micro benchmarks

A bug was introduced when migrating to the v2 API to execute JavaScript
snippets in Telemetry. The old timeout used inconsistent defaults on
different methods, and the migration caused the timeout to drop from 90
to 60 seconds.

Rather than relying on an unseen defualt, specify an explicit timeout
on the non-obvious expression that takes a long time to evaluate.

TBR=nednguyen@google.com
BUG=691751
==========

to

==========
Fix timeout in rasterize_and_record_micro benchmarks

A bug was introduced when migrating to the v2 API to execute JavaScript
snippets in Telemetry. The old timeout used inconsistent defaults on
different methods, and the migration caused the timeout to drop from 90
to 60 seconds.

Rather than relying on an unseen defualt, specify an explicit timeout
on the non-obvious expression that takes a long time to evaluate.

TBR=nednguyen@google.com
BUG=691751

Review-Url: https://codereview.chromium.org/2691023003
Cr-Commit-Position: refs/heads/master@{#450325}
Committed:
https://chromium.googlesource.com/chromium/src/+/58b5ae9d8d96fd72374c5ee63a7c...
==========

[commit-bot: I haz the power, 2017-02-14 11:54:38]

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