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

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


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

Android Builder Perf

Assigning to sheriff gbiv@chromium.org because this autoroll is the only CL in range:
Roll AFDO from 69.0.3496.0_rc-r1 to 69.0.3497.0_rc-r1

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context:  https://crbug.com/805539 

The AutoRoll server is located here: https://afdo-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=gbiv@chromium.org

Change-Id: I344ad6b0faacde7ebac8e31f774f0d55c4ba8253
Reviewed-on: https://chromium-review.googlesource.com/1145000
Reviewed-by: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#576824}

Uh, wow. Thanks for this.

I knew that the Linux bots were shaky a few weeks ago, but the yelling stopped, so I assumed that things calmed down. The linux-size bots that normally ping me appear to have no new data within the last 10 days (issue 866130), though, so that sort of explains the lack of pings. :)

I'll reprioritize this investigation to see what's going wrong. Some turbulence is expected from AFDO, but not this much.

Thank you again for the heads-up!