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

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


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

android-nexus5x-perf

blink_perf.owp_storage - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

kraken - Benchmark documentation link:
  None

jetstream - Benchmark documentation link:
  None

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

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

Re-enable ARC IMEs that were auto-disabled when toggling to laptop mode by yusukes@chromium.org
https://chromium.googlesource.com/chromium/src/+/fcc50c50a5199456b025150012516b0f0e21a4ae
5120 → 5128 (+7.75)

Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/fcfe9a6f17f02771890c03d666dcebf560eca909
5130 → 6903 (+1773)

Assigning to sheriff sullivan@chromium.org because "Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits)" is a roll.

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

Looking at pinpoint, I believe this is entirely caused by "Limit CPU/GPU frequency for Nexus 5X". Marking WontFix as this is expected.