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

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


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

chromium-rel-win7-gpu-intel

===== 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@397456  29164.9  1506.1   18  good
chromium@398038  28915.6  465.679  18  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 618669

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests dromaeo.domcorequery
Test Metric: dom/dom
Relative Change: 1.11%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/940
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9010328000742371600


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

| 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 failed bisect on the intel gpu instead of ATI

Closing.  Bisects aren't reproducing and the range covers way too many changes to narrow down by hand.