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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsJmOtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8KKVqAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Lq7qQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PeMpgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMvp5ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMv2-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8JnupQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsKfE5AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8IjCtAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMu99wgM


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

chromium-webrtc-rel-win10
chromium-webrtc-rel-win8

philipel@: Could these regressions have been caused by your CL https://codereview.webrtc.org/2652043005?

Yes, this is due to the new jitter buffer.

Re #3: Does that mean it should be closed as won't fix?

Removing R-V-G label (was set upon bug filing because the bot was incorrectly configured as internal)

All stats recovered, closing.