Revision range first seen: ??????

Link to failing run: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_cq/builds/705

Link to example failing step log: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_cq/builds/705/steps/page_cycler_v2.intl_ar_fa_he/logs/stdio

It seems as if all page_cycler_v2 benchmarks failed on that test run.

Excerpt from example failing step log:

Exception raised when cleaning story run: 

Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at /b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:110
    test.DidRunStory(state.platform)
  DidRunStory at /b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:306
    platform.tracing_controller.StopTracing()
  StopTracing at /b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:47
    return self._tracing_controller_backend.StopTracing()
  StopTracing at /b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:108
    self._IssueClockSyncMarker()
  _IssueClockSyncMarker at /b/c/b/android_s5_perf_cq/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:203
    self._RecordIssuerClockSyncMarker)
  RecordClockSyncMarker at /b/c/b/android_s5_perf_cq/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

It appears as if Chrome is crashing. nednguyen@, should we remove this from the CQ if it's flaky?

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