First time that I see the failure is at 3e3004db8cdd06fd1d03970872a318684561b53d. Failure appears to happen once out of every ~10 runs. Reaching ~40 runs back from the first failed run is f3536c6161bf81979a5da0c497b59821010e41fd, and it seems like the failure definitely should have happened at that revision. Going to kick off a bisect on that story between those two runs.

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

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

commit 05bda46c67d64407e2de469fee6ce12184c217d7
Author: Charlie Andrews <charliea@chromium.org>
Date: Thu Sep 07 22:09:40 2017

Disable cska-site story on power.typical_10_mobile

TBR=perezju@chromium.org

Bug:  763107 
Change-Id: I50be90dde99221097c432081f7b57b4cffa5e779
Reviewed-on: https://chromium-review.googlesource.com/655814
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#500407}
[modify] https://crrev.com/05bda46c67d64407e2de469fee6ce12184c217d7/tools/perf/benchmarks/power.py

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : power.typical_10_mobile
  Metric       : idle_wakeups_total/http___www.rg.ru_2014_10_21_cska-site.html

Revision             Exit Code      N
chromium@494844      0 +- N/A       20      good
chromium@498248      0 +- N/A       20      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=http...www.rg.ru.2014.10.21.cska.site.html power.typical_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969079075538275776


For feedback, file a bug with component Speed>Bisection

The NextAction date has arrived: 2017-09-08

Actually, it looks like this was just a flake.

                          build                status
test                                                 
de.m.wikipedia.org          508  ---F~---------------
m.chiebukuro.yahoo.co.jp    508  ---F~---------------
m.ebay.com                  508  ---F~---------------
m.facebook.com              508  ---F~---------------
m.huffpost.com              508  ---F~-----F---------
m.ynet.co.il                508  ---F~---------------
siriuslymeg.tumblr.com      508  ---F~---------------
wapbaike.baidu.com          508  ---F~---------------
www.cnn.com                 508  ---F~---------------
www.rg.ru                   508  --FF~---------------

There were some failures at build 505, then www.rg.ru failed once on it's own at 506 for a random device issue (DeviceUnreachableError) [1], so this had nothing to do with the story itself.

[1]: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus6_Perf%2F506%2F%2B%2Frecipes%2Fsteps%2Fpower.typical_10_mobile_on_Android%2F0%2Fstdout

Re-enabling the story now.

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

commit 858e034f3d6a4e41464d450866913da1286f4f65
Author: Juan Antonio Navarro Pérez <perezju@chromium.org>
Date: Fri Sep 08 21:00:00 2017

Revert "Disable cska-site story on power.typical_10_mobile"

This reverts commit 05bda46c67d64407e2de469fee6ce12184c217d7.

Reason for revert: Original failure was actually just a flake.

Original change's description:
> Disable cska-site story on power.typical_10_mobile
> 
> TBR=perezju@chromium.org
> 
> Bug:  763107 
> Change-Id: I50be90dde99221097c432081f7b57b4cffa5e779
> Reviewed-on: https://chromium-review.googlesource.com/655814
> Reviewed-by: Charlie Andrews <charliea@chromium.org>
> Commit-Queue: Charlie Andrews <charliea@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#500407}

TBR=charliea@chromium.org

Change-Id: I318cc683ce6d27b13735e947e45105ce50653022
Bug:  763107 
Reviewed-on: https://chromium-review.googlesource.com/657421
Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#500657}
[modify] https://crrev.com/858e034f3d6a4e41464d450866913da1286f4f65/tools/perf/benchmarks/power.py