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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3f31acc8e25e3cd07364eb53450774608ad8df737bc24d40160951436cbdc695


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

android-nexus5

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstPaint_avg/browse_shopping/browse_shopping_amazon


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=browse.shopping.amazon system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 282ea833bef8dbf11acfa618d06568a910242c4d
  bad_revision : 23d21f4a40156461a6369724ed258db966663ea2

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstPaint_avg/browse_shopping/browse_shopping_amazon

Revision             Result                  N
chromium@502064      797.214 +- 26.3307      6      good
chromium@502163      784.22 +- 46.6982       6      good
chromium@502213      801.771 +- 59.9965      6      good
chromium@502238      776.733 +- 27.9665      6      good
chromium@502250      802.113 +- 60.6048      6      good
chromium@502252      894.611 +- 59.193       6      bad
chromium@502253      892.655 +- 59.0405      6      bad
chromium@502256      887.229 +- 71.7496      6      bad
chromium@502262      894.46 +- 73.4219       6      bad
chromium@502459      896.561 +- 44.8017      6      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=browse.shopping.amazon system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

Trying another bisect but this is going to be quite hard. The metric is very noisy and is hard to tell where it bumped

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstContentfulPaint_avg/browse_shopping/browse_shopping_amazon


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=browse.shopping.amazon system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Going to close this as WontFix, as it's not vanishingly unlikely that this regression is going to get fixed a month after the fact.