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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : IC:duration_avg/browse_social/browse_social_facebook


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.facebook v8.runtimestats.browsing_mobile_classic

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

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


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

Mythri, is this something real? If not, feel free to WontFix.

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : IC:duration_avg/browse_social/browse_social_facebook


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.facebook v8.runtimestats.browsing_mobile_classic

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

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


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

I think these "regressions" are because we moved the benchmarks to the actual classic configuration after this cl: https://codereview.chromium.org/2786633002/. Earlier it was using the turbo configuration. Marking it as wont fix.