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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglpvdrgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglse5rgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtsDvoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtoOJ5goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtsvCtQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9oKvqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9pDJowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9quwsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9oKvqQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9pDJowsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9quwsAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9rqRuwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9qLFtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9vf3pgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9q20swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9pb0oQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9rn4qwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjvCMoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9q2qqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9s24qAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9q3euwoM


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

webrtc-android-tests-nexus5
webrtc-android-tests-nexus72
webrtc-android-tests-nexus9

These are caused by the tests basically being empty for Android, according to.
https://codereview.webrtc.org/2108723004
This will be fixed by activating the tests for Android.