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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglMfVsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1L3XtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1OHkvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1MHjrgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglOOTrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1L2jpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglLvupgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1JTy5AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglPyH8woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglNbolQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1MaX7AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglJPoogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglP_mugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglIeZqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1KG8sAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglPuG6QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1Mzq9QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1NDv7AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglJ_lswkM


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

android-nexus7v2

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

=== Auto-CCing suspected CL author mythria@chromium.org ===

Hi mythria@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : mythria
  Commit : 5d2b312553a7eebfbaf9e92afda4629fb62b5479
  Date   : Thu Feb 23 12:55:16 2017
  Subject: Fix v8 flags in the v8.runtimestats.browse_mobile benchmark.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Optimize:duration_avg/browse_news/browse_news_qq
  Change       : 2901.46% | 8.934 -> 268.150166667

Revision             Result                  N
chromium@452439      8.934 +- 7.37249        6      good
chromium@452465      9.784 +- 3.7004         6      good
chromium@452472      8.2545 +- 6.519         6      good
chromium@452473      6.043 +- 3.52396        6      good
chromium@452474      268.043 +- 72.2428      6      bad       <--
chromium@452475      257.206 +- 81.7747      6      bad
chromium@452478      252.114 +- 65.5682      6      bad
chromium@452490      250.676 +- 84.1024      6      bad
chromium@452541      252.564 +- 73.6633      6      bad
chromium@452642      275.329 +- 39.4199      6      bad
chromium@452845      268.15 +- 47.9281       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.news.qq v8.runtimestats.browsing_mobile

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

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


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

Just a flag change on a bot, not a regression.