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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglP_brwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglPv15QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglP63hggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglJO8swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglKPtvgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglM-kmQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglNXErAkM


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

android-nexus7v2
android-one
chromium-rel-win7-x64-dual

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

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

Suspected Commit
  Author : Ross McIlroy
  Commit : f774d8c56f00de92614886fc4cb541411eff7aa1
  Date   : Tue Mar 07 20:41:12 2017
  Subject: [Flags] Add negation implications for --turbo negative so --no-turbo works.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Optimize:duration_avg/browse_news/browse_news_qq
  Change       : 1157.21% | 21.9933333333 -> 276.503

Revision                           Result                  N
chromium@455226                    21.9933 +- 25.0091      6      good
chromium@455261                    21.0713 +- 20.4052      6      good
chromium@455279                    22.6903 +- 22.4571      6      good
chromium@455288                    28.1272 +- 34.9452      6      good
chromium@455288,v8@f774d8c56f      291.702 +- 38.1462      6      bad       <--
chromium@455288,v8@181a1b4dff      285.743 +- 45.752       6      bad
chromium@455289                    276.512 +- 23.6602      6      bad
chromium@455290                    290.06 +- 36.901        6      bad
chromium@455292                    286.288 +- 31.6629      6      bad
chromium@455296                    276.503 +- 35.1556      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/8985612025164776864

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


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