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

===== BISECT JOB RESULTS =====
Status: completed


===== TESTED REVISIONS =====
Revision         Exit Code  Std Dev  N  Good?
chromium@416253  0          N/A      2  good
chromium@416273  0          N/A      2  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 644826

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.todomvc
Test Metric: v8_compile_full_code_cpu_self_avg/v8_compile_full_code_cpu_self_avg
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4100
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002152137135215376


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5510705002840064

| 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 Tests>AutoBisect.  Thank you!

This is still an issue. Per SheriffOMatic, the rev range is  417643 - 418836 

v8.todomvc failing on chromium.perf/Android Nexus5 Perf (3)

Type: build-failure

Builders failed on: 
- Android Nexus5 Perf (3): 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%283%29

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

===== BISECT JOB RESULTS =====
Status: completed


===== TESTED REVISIONS =====
Revision         Exit Code  Std Dev  N   Good?
chromium@416253  0          N/A      20  good
chromium@419160  0          N/A      20  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 644826

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.todomvc
Test Metric: v8_compile_full_code_cpu_self_avg/AngularJS
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4130
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001331651229100240


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5793584047980544

| 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 Tests>AutoBisect.  Thank you!

Adding jochen@ to this bug, as he seems to have written the benchmark.

Actually, just going to assign this to jochen@. jochen@, feel free to redirect to a better location.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/953d22d019924c8fce8264512390fa6507ed34af

commit 953d22d019924c8fce8264512390fa6507ed34af
Author: charliea <charliea@chromium.org>
Date: Tue Sep 20 15:03:50 2016

Disable v8.todomvc on Samsung Galaxy S5s

The benchmark is failing about 1/3 of the time on the S5s.

TBR=nednguyen@google.com
BUG= 644826 

Review-Url: https://codereview.chromium.org/2349283003
Cr-Commit-Position: refs/heads/master@{#419763}

[modify] https://crrev.com/953d22d019924c8fce8264512390fa6507ed34af/tools/perf/benchmarks/v8.py