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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgv4aBvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3-v1pwoM


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

linux-release

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N    Good?
chromium@439490  2.70862  12.0359  144  good
chromium@439570  2.74665  12.3989  144  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 677412

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests rasterize_and_record_micro.top_25
Test Metric: rasterize_time/rasterize_time
Relative Change: 1.40%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6962
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8991948999507878096


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

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

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : fmalita
  Commit : a7e84a029b10a5a8c0b0faf4bda87e54187840fb
  Date   : Mon Dec 19 20:01:39 2016
  Subject: Clamp background tiles when possible

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : rasterize_and_record_micro.key_mobile_sites
  Metric       : rasterize_time/rasterize_time
  Change       : 1.10% | 1.9277195122 -> 1.94895528455

Revision             Result                     N
chromium@439490      1.92772 +- 0.00760739      6      good
chromium@439510      1.92589 +- 0.00741533      6      good
chromium@439520      1.92865 +- 0.00284849      6      good
chromium@439525      1.93286 +- 0.0045693       6      good
chromium@439528      1.93187 +- 0.00408614      6      good
chromium@439529      1.95154 +- 0.00275441      6      bad       <--
chromium@439530      1.94611 +- 0.00157035      6      bad
chromium@439570      1.94896 +- 0.00626012      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests rasterize_and_record_micro.key_mobile_sites

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990641728580253440

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6378317285949440


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

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