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

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


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

chromium-rel-mac-hdd

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

===== 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@405455  1974.98  34.585   12  good
chromium@405473  1981.62  45.4022  12  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 629314

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_ja_zh
Test Metric: cold_times/page_load_time
Relative Change: 0.45%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/651
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006757332614244384


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

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

Passing the last few on to the current perf sheriff for triage...

Perf sheriff ping: reminder to follow up on possible performance issues

Perf sheriff ping

One alert, really noisy graph, bisect didn't find anything.