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

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


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

chromium-rel-mac11

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

===== 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@421796  244.54   104.839  18  good
chromium@421825  237.381  72.2245  18  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 651811

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___zol.com.cn_
Relative Change: 14.75%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/933
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000093279119336912


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

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

Kicked new bisect

===== 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@421796  286.026  123.072  18  good
chromium@421825  331.709  93.3915  18  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 651811

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___zol.com.cn_
Relative Change: 21.88%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/941
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999816112754811488


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

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

perf sheriff fixit: unsetting owners of bugs owned by sheriffs to clarify the sheriffing rotation triages the bugs.

Archiving as bisection is difficult and there's been no movement.