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

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


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/103b41bbe40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/103b41bbe40000

Build internal android targets in telemetry_chrome_test. by jbudorick@chromium.org
https://chromium.googlesource.com/chromium/src/+/e0c7bc0e869c70995d8b53d9a22e68294f07c7f2
tasks_per_frame_total_all: 48.54 → No values

Revert "Build internal android targets in telemetry_chrome_test." by jbudorick@chromium.org
https://chromium.googlesource.com/chromium/src/+/c7539ef6291836eff22077b38ae55bb62f536b99
tasks_per_frame_total_all: No values → 49.33

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

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

hmmm, so probably the thing that regressed the metric happened between the above 2 CLs during which the metric cannot be computed. I'll try to rerun pinpoint with patching the revert CL.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/10b64f7fe40000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/10b64f7fe40000