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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqLq3_QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6IbKvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqOX8tAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqOba5AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqKuEuwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqP3OtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6PDiqgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqOvMqQkM


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

webrtc-android-tests-nexus5-kitkat
webrtc-linux-large-tests

Um.. "level_controller_call_durations_48000_48000_48000_48000Hz_1_channels_total/SimpleLevelControlViaApm"
Doesn't sound video-related at all?

re #2: No, I agree. And, those guys seems to be all recovered. Feel free to detach them from this bug and mark them as ignore instead.

This bug seems to only point to audio level thingys. Should I just close this bug as wai then?

It includes screenshare_slides_vp9_2sl too. Those are not recovered, right?

Bah! chromeperf.appspot.com, y u no reuse login token from bugs.chromium.org!? :(

Have looked at this, but I can't get it to make any sense. The only change in that blame list that looks even remotely related just adds another VP9 test, but no other code is changed. There's nothing I think looks suspicious in chrome either. No libvpx roll or anything of the sort.

There are also no signs of a regression on any other platform. Including the nexus5 but. It's only visible on nexus5-kitkat. Extra test was just enough to trigger heat throttling or something on the physical device?

jianj@, can you have a look? Maybe make a speculative revert to see if it helps?

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

These seem to have recovered, closing.