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

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


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

android-nexus9
chromium-rel-win10

===== 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@402383  19413.3  549.901  18  good
chromium@402394  19309.5  558.196  18  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 623975

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: Total/Total
Relative Change: 1.12%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1848
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008598412001598848


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

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

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is most likely a dupe of the  issue 624309 .

Duping against  bug 624309  as suggested in #5 because these graphs get better at the exact same revisions as the one in that bug.