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

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


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

chromium-rel-win7-dual

===== 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 Value  Std. Dev.   Num Values  Good?
chromium@386108         183.482145  4.183712    18          good
chromium@386126         183.677238  5.056412    18          bad

Bisect job ran on: win_perf_bisect
Bug ID: 602331

Test Command: python src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests page_cycler.morejs
Test Metric: warm_times/page_load_time
Relative Change: 0.90%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6456
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015660532046334368


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

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

re-kicked bisect with modified range.

Closing.  The reference and measured results are both moving in tandem, right on top of each other.  Looks like an infrastructure variability.