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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzPLqrgoM


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

android-one

===== 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@394424  1.82147  0.0784675  18  good
chromium@394507  1.79017  0.0596283  18  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 613431

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_mobile_sites_smooth
Test Metric: thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
Relative Change: 3.04%
Score: 0

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


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

| 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!

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Trying a wider bisect.

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


===== SUSPECTED CL(s) =====
Subject : Disable thread-safe Send on ChannelMojo
Author  : rockot
Commit description:
  
The world is not yet ready for thread-safe Send. D:

BUG= 612944 
TBR=jam@chromium.org

Review-Url: https://codereview.chromium.org/1991913003
Cr-Commit-Position: refs/heads/master@{#394568}
Commit  : ff0d8038dd81bb025313a393cb8a6fcde9a79603
Date    : Wed May 18 22:04:53 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@394424  1.78906  0.0534653  5  good
chromium@394509  1.80427  0.045604   5  good
chromium@394551  1.86098  0.112807   5  good
chromium@394562  1.81577  0.0869815  5  good
chromium@394567  1.78175  0.0680246  5  good
chromium@394568  2.23363  0.0988742  5  bad    <--
chromium@394569  2.20531  0.0918485  5  bad
chromium@394570  2.23472  0.0627397  5  bad
chromium@394572  2.23275  0.0454266  5  bad
chromium@394593  2.17262  0.0478912  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 613431

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_mobile_sites_smooth
Test Metric: thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
Relative Change: 21.44%
Score: 99.9

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


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

| 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!