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

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


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

Android Nexus6 WebView Perf
android-nexus5x-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/168c01abe40000

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

Build internal android targets in telemetry_chrome_test. by jbudorick@chromium.org
https://chromium.googlesource.com/chromium/src/+/e0c7bc0e869c70995d8b53d9a22e68294f07c7f2
tasks_per_frame_total_all: 31.24 → 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 → 34.32

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

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

Adding and then reverting build targets did not cause this regression.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/146f6620140000

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

kicked other bisects for different tests.
let's see what happens.

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

OK, since no regression was detected within a wider revision range, let's close as WontFix.