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

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


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

android-nexus5

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

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

Roll AFDO from 68.0.3437.0_rc-r1 to 68.0.3437.0_rc-r2 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/57419a742ce4b38b147a543e6be7ca165f675af8

Assigning to sheriff gbiv@chromium.org because "Roll AFDO from 68.0.3437.0_rc-r1 to 68.0.3437.0_rc-r2" is a roll.

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

Looks like a flake, since it recovered with today's AFDO roll. So, I don't plan on taking any action on this before the branchpoint, but I've got a general "make benchmarks less flaky with AFDO rolls" goal at the moment, so I'll include this in that.

Thanks for the heads-up.

 Issue 845854  has been merged into this issue.