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

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


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

android-webview-nexus5X
linux-perf

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

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

Add support for reporting muted watch time. by dalecurtis@chromium.org
https://chromium.googlesource.com/chromium/src/+/bec82e76f5f09ffdf96dc7c3045c6b581912972b
2556 → 2510 (-46.71)

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
2519 → 3261 (+742.5)

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

Thanks!

3437-rc2 was a pretty terrible roll; looks like everything's back to normal after the roll from 3437-rc2 to 3438 in r560993.

(Marking this as fixed, as I intended to do in the last reply...)