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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiMHQoQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8NXjsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8IeTqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiIqFoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8LvPrQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiJH8tQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiJa_sQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8P2o7ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8NmG6wsM


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

webrtc-mac-large-tests
webrtc-win-large-tests

philipel@: This regressions seems to possible be related to your CL https://codereview.webrtc.org/2656983002. Could you please take a look?

I heavily suspect this is due to this CL: https://chromium.googlesource.com/external/webrtc/+/f00497c5732b99c42f66023a5b0940c7418d14ed

The following revision refers to this bug:
  https://chromium.googlesource.com/external/webrtc.git/+/7f08e822512f911dd30722d9575eccd2318c8016

commit 7f08e822512f911dd30722d9575eccd2318c8016
Author: stefan <stefan@webrtc.org>
Date: Tue Jan 31 15:49:28 2017

Fix per regression in probing.

BUG= chromium:687030 

Review-Url: https://codereview.webrtc.org/2664193002
Cr-Commit-Position: refs/heads/master@{#16381}

[modify] https://crrev.com/7f08e822512f911dd30722d9575eccd2318c8016/webrtc/modules/pacing/bitrate_prober.cc