Revision range first seen: ?????
Link to failing step log: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_cq/builds/706/steps/smoothness.gpu_rasterization.tough_filters_cases/logs/stdio

Buildbot page: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_cq/builds/706

Note that these benchmarks failed for https://codereview.chromium.org/2520903003/, which was a simple Telemetry change to disable some benchmarks.

Failing benchmarks: 
smoothness.gpu_rasterization.polymer 
smoothness.gpu_rasterization.top_25_smooth
smoothness.gpu_rasterization.tough_filters_cases
smoothness.gpu_rasterization.tough_path_rendering_cases 

(Note that no benchmarks are failing on the reference build.)

Excerpt from logs:

Traceback (most recent call last):
  File "/b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 80, in _RunStoryAndProcessErrorIfNeeded
    state.WillRunStory(story)
  File "/b/c/b/android_s5_perf_cq/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_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 214, in WillRunStory
    self._StartBrowser(page)
  File "/b/c/b/android_s5_perf_cq/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_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 174, in _StartBrowser
    self._browser = self._possible_browser.Create(self._finder_options)
  File "/b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/android_browser_finder.py", line 127, in Create
    browser_backend, self._platform_backend, self._credentials_path)
  File "/b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py", line 55, in __init__
    self._browser_backend.Start()
  File "/b/c/b/android_s5_perf_cq/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_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/android_browser_backend.py", line 140, in Start
    self._WaitForBrowserToComeUp()
  File "/b/c/b/android_s5_perf_cq/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_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/chrome_browser_backend.py", line 162, in _WaitForBrowserToComeUp
    raise exceptions.BrowserConnectionGoneException(self.browser, e)
BrowserConnectionGoneException: Timed out while waiting 120s for HasBrowserFinishedLaunching.
Found Minidump: True

This certainly makes it look like the browser crashed.

nednguyen@, any suggested next steps?

Shouldn't we remove the Android S5 perf CQ altogether, given that the Android S5 perf bots are removed?