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

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


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

android-nexus6
android-nexus7v2

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

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

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Total:duration_avg/browse_news/browse_news_flipboard


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

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

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


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

Hmmm, the increased flakyness is interesting, I can't see the same thing on other benchmarks on this bot. Any clue?

Simon, any clue what "unkown reasons" mean?

Definitely a blink issue, JS times on the very same bots yield clean numbers:
https://chromeperf.appspot.com/report?sid=648a8db67ee88971f8b5ecba88d0f916a7c82053c06cccac698040d1914845eb

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

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

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


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Blink C++:duration_avg/browse_news/browse_news_flipboard


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

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

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


| 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/8983066176651750320

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

Hi fserb@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 : fserb
  Commit : ea6a16123f90b39e8de13c65cf04935107d252ae
  Date   : Wed Mar 22 04:15:36 2017
  Subject: Disables EnableAccelerationToAvoidReadbacks due to regression

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Blink C++:duration_avg/browse_news/browse_news_flipboard
  Change       : 146.52% | 3924.72764286 -> 9675.27992857

Revision             Result                  N
chromium@458619      3924.73 +- 1570.88      14      good
chromium@458621      3972.11 +- 960.411      9       good
chromium@458622      4008.99 +- 834.498      9       good
chromium@458623      8694.15 +- 10136.4      9       bad       <--
chromium@458626      12000.6 +- 7238.99      6       bad
chromium@458633      10894.0 +- 4491.28      6       bad
chromium@458647      9640.91 +- 7373.04      6       bad
chromium@458674      9675.28 +- 11650.0      14      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.flipboard v8.runtimestats.browsing_mobile_classic

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

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


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

re: #c5

Means the failure isn't surfaced well to either bisect or the dashboard, in this case it failed before the bisect even ran during the bot_update stage.

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

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

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


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Blink C++:duration_avg/browse_news/browse_news_flipboard


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

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

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


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