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

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


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

Android Nexus5X WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17c3ff2de40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17c3ff2de40000

Telemetry: remove old cpu_per_frame metrics by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/af5198be3516b3e7e5f54e9cdf6dc2882e1e4100
thread_total_all_cpu_time_per_frame: 0 → No values

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

0 -> No values is not a real regression. I'll start another pinpoint with a narrower range.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14b27f87e40000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14b27f87e40000

All of the runs failed. The most common error (20/20 runs) was:
ReadValueError: Could not find values matching: {'story': u'geo_apis', 'histogram': u'thread_total_all_cpu_time_per_frame'}

Weird! The perf dashboard shows a value at 605021:

https://chromeperf.appspot.com/report?sid=b40aea3827203b318caf92910e3489dfacd096b3f9b05903561822cbca29e0fc&start_rev=602962&end_rev=607184

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17424573e40000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/17424573e40000

All of the runs failed. The most common error (20/20 runs) was:
ReadValueError: Could not find values matching: {'story': u'geo_apis', 'histogram': u'thread_total_all_cpu_time_per_frame'}