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

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


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

android-nexus5x-perf

speedometer2 - Benchmark documentation link:
  None

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

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

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
163.4 → 234.8 (+71.46)

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

Benchmark documentation link:
  None

 Issue 881762  has been merged into this issue.

 Issue 880750  has been merged into this issue.

 Issue 880748  has been merged into this issue.

 Issue 880747  has been merged into this issue.

 Issue 880751  has been merged into this issue.

WontFixing as this is almost certainly due to:

pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X