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

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


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

chromium-rel-mac-retina

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

===== 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@422623  233.316  27.2099  18  good
chromium@422671  224.861  30.5505  17  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 654459

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_site_isolation.basic_oopif
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___booking.com
Relative Change: 5.71%
Score: 0

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


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

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

Possibly just noise, should be closed if bisect doesn't find anything the second time.

===== 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@422623  279.246  16.5992  18  good
chromium@422671  271.957  24.1561  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 654459

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_site_isolation.basic_oopif
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___booking.com
Relative Change: 5.65%
Score: 0

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


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

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