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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5b6muAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglYyioAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglfDe6QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5cWAtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpa_qjAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5dSzywkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1Zr4swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtaLIrgoM


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

android-nexus5

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@414880  80.1149  5.94847  7   good
chromium@416440  80.541   7.27892  10  good
chromium@417240  84.6471  8.53519  12  good
chromium@417620  86.0685  7.79128  9   good
chromium@417810  85.6345  5.4381   8   good
chromium@418000  97.2146  6.95336  12  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 653842

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_mobile_ignition
Test Metric: v8-gc-latency-mark-compactor_sum/v8-gc-latency-mark-compactor_sum
Relative Change: 16.07%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4203
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999463941452458832


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

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile_ignition
  Metric       : v8-gc-latency-mark-compactor_sum/v8-gc-latency-mark-compactor_sum

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1096190784ad7c30c25929df0709d4878c0a4a45..dee727c8ac26512c3f6fe852fdefb00186909a89


Revision             Result                  N
chromium@414880      80.1149 +- 5.94847      7       good
chromium@416440      80.541 +- 7.27892       10      good
chromium@417240      84.6471 +- 8.53519      12      good
chromium@417620      86.0685 +- 7.79128      9       good
chromium@417810      85.6345 +- 5.4381       8       good
chromium@418000      97.2146 +- 6.95336      12      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_mobile_ignition

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982632447087481056

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5254527928762368


| 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 Speed>Bisection.  Thank you!

This regression has been included in a stable release and that stable channel is now deprecated. I'm closing this so that we won't have unresponsive performance regressions in the future.