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

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


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

android-nexus5X

===== 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@394751  11.9872  0.0666946  12  good
chromium@394769  11.9882  0.0930681  12  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 615195

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/185
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011568256142852944


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

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

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


===== SUSPECTED CL(s) =====
Subject : cc : Track ids for which active opacity always wins on property trees
Author  : jaydasika
Commit description:
  
And then use this for partial sync of property trees at the time of
activation. PaintedScrollbarLayer and SolidColorScrollbarLayer currently
need the active tree opacity to win at activation.

BUG= 611899 
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review-Url: https://codereview.chromium.org/1991523002
Cr-Commit-Position: refs/heads/master@{#394784}
Commit  : ae9b7a05e087905774fb29807281fa771711ff3b
Date    : Thu May 19 16:14:26 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@394751  11.9873  0.100799   5  good
chromium@394775  11.8056  0.0518666  5  good
chromium@394781  11.9026  0.134771   5  good
chromium@394783  11.9214  0.0503005  5  good
chromium@394784  12.6618  0.0611822  5  bad    <--
chromium@394787  12.6743  0.0932138  5  bad
chromium@394799  12.5953  0.0682822  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 615195

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/186
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011568248907969648


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

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