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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : ???
  Metric       : TraceEventPerfTest.Submit_10000_TRACE_EVENT0_in_traceable_tasks/flush


To Run This Test
  src/build/android/test_runner.py gtest --release -s tracing_perftests --verbose

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

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


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.