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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : ???
  Metric       : TraceEventPerfTest.Submit_10000_TRACE_EVENT_with_TracedValue/events_with_value


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/8958212401467914096


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.