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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : speedometer-ignition
  Metric       : Total/Total
  Change       : 0.84% | 49340.7492857 -> 49556.2313095

Suspected Commit Range
  5 commits in range
  https://chromium.googlesource.com/chromium/src/+log/80aedca1fd5f6a735391ee96f7dbe24220d05782..3988b62ce2aa6071455afd06e06b94af7a044dd9


Revision             Result                  N
chromium@443146      49340.7 +- 667.064      14       good
chromium@443178      49333.4 +- 1044.67      21       good
chromium@443194      49256.6 +- 1076.7       21       good
chromium@443195      ---                     ---      build failure
chromium@443196      ---                     ---      build failure
chromium@443197      ---                     ---      build failure
chromium@443198      ---                     ---      build failure
chromium@443199      49510.3 +- 908.485      14       bad
chromium@443210      49556.2 +- 691.107      14       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 speedometer-ignition

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

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


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

I'm seeing a regression on speedometer-ignition on nexus 5 after, where it seems
https://codereview.chromium.org/2566043004 could be a cause. Could you take a look please?

I don't see how my CL could have an impact on this test.
It just adds some UMA at page load.
There doesn't seem to be a regression on non-ignition bots.

Taking another look at the bisect results, the variance seems too high to call this your CL. The graphs seem to recover (at least, up to the next regression), so marking wontfix.