Revision range first seen: ????? (failing before 10/23)
Link to failing step log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus9_Perf__2_%2F3435%2F%2B%2Frecipes%2Fsteps%2Fsmoothness.gpu_rasterization.tough_scrolling_cases.reference%2F0%2Fstdout

It doesn't seem that the same test case is always failing: I've seen both 15000px/second and 30000px/second fail. Some user story is failing at least 50% of the time, and has been since at least 10/23.

The failure log indicates that Chrome is crashing:

Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at /b/rr/tmp07BZKa/w/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:110
    test.DidRunPage(state.platform)
  traced_function at /b/rr/tmp07BZKa/w/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:75
    return func(*args, **kwargs)
  DidRunPage at /b/rr/tmp07BZKa/w/src/tools/perf/measurements/smoothness.py:65
    self._tbm.DidRunStory(platform)
  DidRunStory at /b/rr/tmp07BZKa/w/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:309
    platform.tracing_controller.StopTracing()
  StopTracing at /b/rr/tmp07BZKa/w/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:47
    return self._tracing_controller_backend.StopTracing()
  StopTracing at /b/rr/tmp07BZKa/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:108
    self._IssueClockSyncMarker()
  _IssueClockSyncMarker at /b/rr/tmp07BZKa/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:203
    self._RecordIssuerClockSyncMarker)
  RecordClockSyncMarker at /b/rr/tmp07BZKa/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:175
    raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients')
ChromeClockSyncError: Cannot issue clock sync. No devtools clients

I'm going to disable this benchmark on Android until this gets fixed. ericrk@, could you take responsibility for making sure that the right person investigates why this is happening?

If the test is disabled, please downgrade to Pri-2.