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

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


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

android-galaxy-s5
android-nexus7v2
android-nexus9

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2073
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Pretty sizable regression, feel like we should be able to find this one. Sent off some more bisects.

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2119
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2158
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

perf sheriff fixit: unsetting perf sheriffs as bug owners to clarify the rotation triages the bugs.

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@414586  N/A   N/A      0  good
chromium@414626  N/A   N/A      0  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 642120

Test Command: src/build/android/test_runner.py gtest --release -s cc_perftests --verbose
Test Metric: ParamTraits deserialization/min_frame_deserialization_time: DelegatedFrame_ManyRenderPasses_10_500
Relative Change: 0.00%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3556
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993178754328149456


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

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

These will all be invalid as they are specific to Samsung S5s, which we do not trust to give us a signal and have subsequently removed from the waterfalls. If you think this regression is real, please re-open.