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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxpb0tAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxqWmugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxuH9ugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxozYtgkM


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

chromium-webrtc-trunk-tot-rel-linux
chromium-webrtc-trunk-tot-rel-mac

I don't think anything of importance really changed, the only difference now is that we always print Total_skiped.

https://codereview.chromium.org/2912933002

Rather than failing completely and not print any of the MAX stats I changed it to always print even if it breaks the loop.

We are going to investigate this script more since we suspect a bug related to max counters.