Oh, nvm, looks like it was added on build 5157. It never ran before that. I guess it just has never passed?

Looks like we should just increase the timeout (maybe just for Android One's if possible)

Traceback (most recent call last):
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 88, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 302, in RunStory
    self._current_page, self._current_tab, results)
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_One_Perf__3_/src/tools/perf/benchmarks/jetstream.py", line 59, in ValidateAndMeasurePage
    """, timeout=600)
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 191, in WaitForJavaScriptCondition
    return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs)
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_One_Perf__3_/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 294, in WaitForJavaScriptCondition
    e.message + '\n' + debug_message)
TimeoutException: 
Exception thrown when trying to capture console output: TimeoutException('',)

(INFO) 2017-05-09 06:58:52,355 cmd_helper._ValidateAndLogCommand:161  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 01e15d4fa2659c8d shell '( log -p i -t Telemetry '"'"'START http://browserbench.org/JetStream/'"'"' );echo %$?'

(INFO) 2017-05-09 07:04:36,024 cmd_helper._ValidateAndLogCommand:161  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 01e15d4fa2659c8d shell '( log -p i -t Telemetry '"'"'END http://browserbench.org/JetStream/'"'"' );echo %$?'

This test appears to take 6 minutes on an N5X. Soo 10 minute timeout should almost definitely be raised.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/46e4aaeb0af3b53b01df4cfaf6b584b412ba05b7

commit 46e4aaeb0af3b53b01df4cfaf6b584b412ba05b7
Author: mikecase <mikecase@chromium.org>
Date: Wed May 10 16:06:14 2017

Increase jetstream benchmark timeout.

This benchmark is timing out on Android One perf bot.
Increasing timeout to 20 minutes.

BUG= 719971 

Review-Url: https://codereview.chromium.org/2871573008
Cr-Commit-Position: refs/heads/master@{#470592}

[modify] https://crrev.com/46e4aaeb0af3b53b01df4cfaf6b584b412ba05b7/tools/perf/benchmarks/jetstream.py

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.