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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiqqcrQoM


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

chromium-webrtc-trunk-tot-rel-mac

Hi Alex and Alessio,

This is a really small regression, so if we can't find out a cause it's probably okay to ignore (note that a very similar looking regression happened a while ago and was ignored by the sheriff). I cannot find any related CLs close to the regression (but that can be hard tricky for WebRTCChromiumFYI regressions), but the test reminds me a lot of your recent AGC work. Did either of you land any CLs recently that could have (very slightly) changed this stat? You can look at the code for the test here: https://cs.chromium.org/chromium/src/chrome/browser/media/webrtc/webrtc_audio_quality_browsertest.cc?l=763

We haven't started landing anything yet. Shouldn't be us :)

Okay, thanks for the reply, I think it's safe to ignore this in that case. I'll just close this.