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

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


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

android-nexus6

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

=== 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_nexus6_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_max/browse_social/browse_social_twitter
  Change       : 70.55% | 21.7018333333 -> 37.0125

Suspected Commit Range
  41 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ec69818af043485daccd4d4f43718390e9ddcb08..e4dd371c464f77b6fbef56d212f7de71e03bf002


Revision             Result                  N
chromium@452027      21.7018 +- 5.09286      6        good
chromium@452028      ---                     ---      build failure
---                  ---                     ---      too many build failures to list
chromium@452067      ---                     ---      build failure
chromium@452068      33.9785 +- 12.4558      6        bad
chromium@452096      36.3962 +- 12.5507      6        bad
chromium@452164      37.0125 +- 11.1297      6        bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.browsing_mobile

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

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


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

graphs recovered

Some graphs did not recover. Reopening.

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_sum/browse_news/browse_news_nytimes

Revision             Result                  N
chromium@451825      1504.69 +- 1173.21      21      good
chromium@452845      1554.08 +- 1162.38      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.browsing_mobile

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

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


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

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

The graphs recovered.