I'm seeing this as long ago as https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus9%20Perf%20%282%29/builds/3521 (431055 - 431094), which is basically as far back as our bot history goes, so it may go back even further. siriuslymeg.tumblr.com appears to cause more frequent failures, though.

This appears to have started somewhere between builds #3621 and #3626. I'm going to kick off a bisect between builds 433988 (good) and 434271 (bad).

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

===== BISECT JOB RESULTS =====
Status: started


===== TESTED REVISIONS =====
Revision         Exit Code  Std Dev  N   Good?
chromium@434050  0          N/A      10  good
chromium@434271  0          N/A      10  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 671631

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=siriuslymeg.tumblr.com power.gpu_rasterization.typical_10_mobile
Test Metric: application_energy_consumption_mwh/http___siriuslymeg.tumblr.com_
Relative Change: 0.00%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2307
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993999358092017568


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

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

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

commit 031d2ac71d1a837fe7f67e8c14c2d32f58fec107
Author: charliea <charliea@chromium.org>
Date: Tue Dec 06 20:47:39 2016

Disable power.gpu_rasterization.typical_10_mobile on Nexus 9

R=sullivan@chromium.org
CC=rnephew@chromium.org,nednguyen@chromium.org,erikchen@chromium.org
BUG= 671631 

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

[modify] https://crrev.com/031d2ac71d1a837fe7f67e8c14c2d32f58fec107/tools/perf/benchmarks/power.py

 crbug.com/673440  for "started" status.

Somehow, my disable CL failed to have any effect :-/ Going to kick off a bisect now anyhow to see if we can identify the culprit (from a long, long time ago).

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

=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : power.gpu_rasterization.typical_10_mobile
  Metric       : application_energy_consumption_mwh/application_energy_consumption_mwh

Revision             Exit Code      N
chromium@434050      0 +- N/A       10      good
chromium@434271      0 +- N/A       10      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 power.gpu_rasterization.typical_10_mobile

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

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


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

It looks like I accidentally disabled power.typical_10_mobile instead of power.gpu_rasterization.typical_10_mobile in my previous CL, although I suspect that both benchmarks are problematic because the page set is crashing on Nexus 9. I'm going to submit a CL that also disables power.gpu_rasterization.typical_10_mobile now.

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

commit 3787fa693e2297fa5aae2891cc3a2087eb7e6833
Author: charliea <charliea@chromium.org>
Date: Fri Jan 13 19:03:46 2017

Disable power.gpu_rasterization.typical_10_mobile on Nexus 9

This benchmark has been flaky since early December.

BUG= 671631 

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

[modify] https://crrev.com/3787fa693e2297fa5aae2891cc3a2087eb7e6833/tools/perf/benchmarks/power.py

Only nexus9. Wontfix.