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

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


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

chromium-webrtc-rel-7

Nope sorry, but I suspect this might have something to do with it: https://chromium.googlesource.com/external/webrtc/trunk/webrtc/+/732c1da43e21f2c411ac276d48ffffeecdd7891a

Erik, PTAL.

Here is the commit range of the latests webrtc update for the ChromiumWebRTC bot as the regression happened:
https://chromium.googlesource.com/external/webrtc/trunk/webrtc/+log/8ff7cecc5bc21065d2ca7ae4b65a2f28887466e0..2a4b1756ee43486e2bf1e0194a2d5850ce2ae050

I'd say this is not related to my cl. I only renamed a few methods and added a new unit test, no functionality was changed.

Thanks! Since the values are now back to what they were before, I'll close as won't fix.