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

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


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

Android Nexus5 Perf
android-nexus5x-perf

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

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

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/1400ef13640000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.

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

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

Roll AFDO from 71.0.3539.0_rc-r1 to 71.0.3540.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/965addab71f63f4e44547d77bd0c1def7b44b099
21.12 → 20.47 (-0.6577)

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
20.16 → 14.65 (-5.509)

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:
  https://bit.ly/blink-perf-benchmarks

This is expected from the following CL in the roll:
pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X

Thanks for taking a look.