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

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


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

android-one

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstMeaningfulPaint_avg/Regular-3G/https___www.google.com.br_search?q_flor_q_Entrega+de+flores_start_10

Revision             Result                  N
chromium@457799      1133.69 +- 508.083      21      good
chromium@457894      1131.29 +- 659.403      21      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=https...www.google.com.br.search.q.flor.q.Entrega.de.flores.start.10 loading.mobile

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.