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

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


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

android-nexus5x-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/138d2553640000

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

Do not use components/arc/common in non CrOs builds by mcasas@chromium.org
https://chromium.googlesource.com/chromium/src/+/e865a56bd15e1ff2acc8f6a0a919036c3f6760b8
196.1 → No values

Revert "Do not use components/arc/common in non CrOs builds" by mcasas@chromium.org
https://chromium.googlesource.com/chromium/src/+/34cd555a197d2296d99cf63d4d83b7297dc6a931
No values → 199.2

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

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

I landed a fixed version of the CL landed and reverted (see #3),
which, I think, hasn't regressed any metrics, so this should be
a WontFix, right?

From the bisect results, it looks like the first CL broke the perf bot and the revert fixed it.