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

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


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/17b380a7e40000

📍 Found significant differences after each of 4 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/17b380a7e40000

Update top bar visibility against a list of eligible domains from intent extra. by chuanl@google.com
https://chromium.googlesource.com/chromium/src/+/168554a77f99988f976626b1605276d1e7279347
avg_surface_fps: 60.19 → 60.14 (-0.05122)

Telemetry: finally move rendering to TBMv2 by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/05af02c8afe6a0fdc3d5e32ff88632fa15f5c567
avg_surface_fps: 60.14 → No values

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

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

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

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

From the pinpoint results above (also see  issue 906540 ), it looks like the move of rendering to TBMv2 at  r605718 causes some of the metrics to be no longer reported. Some of the affected metrics appear to be:

- avg_surface_fps
- frame_lengths
- jank_count
- mean_frame_time_renderer_compositor
- mean_pixels_approximated
- mean_pixels_checkerboarded

See: https://storage.cloud.google.com/results2-public/17b380a7e40000.html

Are these expected?

Also note fixing this might be blocked on  issue 906540 , which caused *all* other metrics to also vanish.