All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=770240

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=8edcfa69961db7e4c30a34bf4cb53e22862c0f49c419a40f1c717703445280d0


Bot(s) for this bug's original alert(s):

android-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8967099926860376736

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : tracing_perftests
  Metric       : TraceEventPerfTest.Submit_10000_TRACE_EVENT_with_TracedValue/events_with_value


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=events.with.value tracing_perftests

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8967099926860376736


For feedback, file a bug with component Speed>Bisection

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.