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

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


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

Android Nexus6 WebView Perf

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

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

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

Roll AFDO from 71.0.3552.6_rc-r1 to 71.0.3553.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/da9e80c415f9fbe79bd53d56ff7a07bd9d585916
359.6 → 337.3 (-22.24)

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

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

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

I count four distinct pieces of AFDO-induced noise in the last month for this one, if I include the recovery + subsequent dip after this bug was filed. :)

Similar story to #4 of  issue 886889 : if the noise continues, I can look into it and see if there's a way to stabilize it. I'll keep hold of this bug until I get a complaint about r591978, though. 

Thanks!

> until I get a complaint about r591978

Yeah... I guess five complaints works, too. :)

Since I assume the r591978 roll is a flake, that brings us to three pieces of AFDO-induced noise for this metric specifically. All of which appear to have recovered.

Closing this out under the assumption that another bug will find its way to me if that number goes back to four.