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

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


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

chromium-rel-win7-x64-dual

Re-kicked with wider range: https://chromeperf.appspot.com/buildbucket_job_status/9009962892638400976

===== 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@398038  231.346  18.0059  18  good
chromium@398156  241.515  3.62439  18  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 618663

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings
Test Metric: insert-before/insert-before
Relative Change: 1.65%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1246
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009962892638400976


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

| 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-kicking again.  The test looks REALLY noisy though and the regression happened over a fairly wide period so not sure we will be able to bisect it.

===== 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@398080  254.559  3.94279  18  good
chromium@398123  252.476  3.65376  18  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 618663

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings
Test Metric: insert-before/insert-before
Relative Change: 0.82%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1247
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009864061404901568


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

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

Kicked off another bisect.

Closing.  Can't bisect and looking through the change log isn't showing anything of interest.