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

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


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

Android Nexus5 Perf

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

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

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

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
frame_times: 20.06 → 21.17 (+1.107)

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

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

eseckler: This one in particular has a pageset (balls_svg_animations) that seem prone to the "missing thread names" issue we saw, if you look at the graph for the entries with a 0 value.

Should be all recovered with http://crrev.com/612360 but it's hard to confirm given the large timeframe where there's no data from the webview bots :/