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

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


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

android-webview-nexus6

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

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

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Mike Reed
  Commit : 7a542c559a6e584107b94e6254ac3c7f9f24b591
  Date   : Tue Apr 11 16:38:17 2017
  Subject: Change bitmapcache to not rely on lockpixels.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame
  Change       : 6.24% | 0.533606701092 -> 0.566906836726

Revision                             Result                      N
chromium@463664                      0.533607 +- 0.0099869       6      good
chromium@463681                      0.535023 +- 0.00583539      6      good
chromium@463690                      0.53676 +- 0.011816         6      good
chromium@463694                      0.538443 +- 0.0148681       6      good
chromium@463694,skia@77443974ea      0.537359 +- 0.0113574       6      good
chromium@463694,skia@7a542c559a      0.563912 +- 0.0121283       6      bad       <--
chromium@463695                      0.566782 +- 0.0101806       6      bad
chromium@463696                      0.562586 +- 0.0126082       6      bad
chromium@463698                      0.565268 +- 0.00713214      6      bad
chromium@463731                      0.566907 +- 0.00675716      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites

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

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


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