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

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


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

webrtc-android-tests-nexus4-lollipop
webrtc-linux-large-tests

Looks like it's due to this CL: https://chromium.googlesource.com/external/webrtc/+/2a8c2f589aa5e757cdb5d5cbb13f4494250ddf11

First graph is audio test, completely unrelated to changes. I could reproduce it on my machine, but the metric in question is 1us larger only for 1st ran. If test is repeated with gtest_repeat, on the second ran it's back to normal and stays like that. I think it's not a bug, but rather executable became to big, some memory got moved around and we get some chache related magic involved. Therefore, I will ignore first graph for audio test.

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

All regressions are not relevant anymore.