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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-ercqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-c62vAoM


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

android-one

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

Won't fix. Ref build moved too.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@418816  3657946  596720   18  good
chromium@418838  3604382  781246   18  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 648654

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests tracing.tracing_with_debug_overhead
Test Metric: Max event size in bytes per second_max/Max event size in bytes per second_max
Relative Change: 3.40%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1625
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000982816254687968


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5002304103645184

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!