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

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


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

chromium-rel-mac-retina
chromium-rel-win10

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

===== 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@422905  124.496  19.6983  18  good
chromium@422923  124.334  20.8746  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 654224

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_es_fr_pt-BR
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___terra.es_
Relative Change: 0.13%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1731
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999350514296900272


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

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

If the next bisect job fails to reproduce a regression, then this should likely be closed.

===== 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@422870  1737.53  339.02   18  good
chromium@422923  1861.34  321.496  18  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 654224

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.typical_25
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___www.theverge.com_2013_3_5_4061684_inside-ted-the-smartest-bubble-in-the-world
Relative Change: 1.58%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/746
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999167591674844448


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

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