Fix BitrateControllerImpl not to ignore BW probe results mid-call.

Fix BitrateControllerImpl not to ignore BW probe results mid-call.

Previously when BitrateControllerImpl::OnDelayBasedBweResult() is
called as result of a probe it was calling
bandwidth_estimation_.SetSendBitrate(), but not
UpdateDelayBasedEstimate(). As result SendSideBandwidthEstimation was
effectively ignoring probe results as it kept the old
delay_based_bitrate_bps_ value, which caps the resulting bitrate.

BUG=webrtc:6332, webrtc:6710
Review-Url: https://codereview.webrtc.org/2481383002
Cr-Commit-Position: refs/heads/master@{#15071}
(cherry picked from commit 26b675625f150be1ebc1a2350d39e5116d214871)

R=stefan@webrtc.org

Committed: https://chromium.googlesource.com/external/webrtc/+/5ff9cd35c5f5052cc7a9c4a63759cf8d86a5234b

[philipel, 2016-11-27 13:00:20]

The CQ bit was checked by philipel@webrtc.org

[commit-bot: I haz the power, 2016-11-27 13:00:28]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-11-27 13:00:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-27 13:00:29]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
Committers are members of the group "project-webrtc-committers".
Note that this has nothing to do with OWNERS files.

[stefan-webrtc, 2016-11-28 10:44:18]

stefan@webrtc.org changed reviewers:
+ stefan@webrtc.org

[stefan-webrtc, 2016-11-28 10:44:18]

lgtm

[philipel, 2016-11-28 12:03:49]

Description was changed from

==========
Fix BitrateControllerImpl not to ignore BW probe results mid-call.

Previously when BitrateControllerImpl::OnDelayBasedBweResult() is
called as result of a probe it was calling
bandwidth_estimation_.SetSendBitrate(), but not
UpdateDelayBasedEstimate(). As result SendSideBandwidthEstimation was
effectively ignoring probe results as it kept the old
delay_based_bitrate_bps_ value, which caps the resulting bitrate.

BUG=webrtc:6332,webrtc:6710

Review-Url: https://codereview.webrtc.org/2481383002
Cr-Commit-Position: refs/heads/master@{#15071}
(cherry picked from commit 26b675625f150be1ebc1a2350d39e5116d214871)
==========

to

==========
Fix BitrateControllerImpl not to ignore BW probe results mid-call.

Previously when BitrateControllerImpl::OnDelayBasedBweResult() is
called as result of a probe it was calling
bandwidth_estimation_.SetSendBitrate(), but not
UpdateDelayBasedEstimate(). As result SendSideBandwidthEstimation was
effectively ignoring probe results as it kept the old
delay_based_bitrate_bps_ value, which caps the resulting bitrate.

BUG=webrtc:6332,webrtc:6710

Review-Url: https://codereview.webrtc.org/2481383002
Cr-Commit-Position: refs/heads/master@{#15071}
(cherry picked from commit 26b675625f150be1ebc1a2350d39e5116d214871)

R=stefan@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/5ff9cd35c5f5052cc7a9c4a63...
==========

[philipel, 2016-11-28 12:03:50]

Committed patchset #1 (id:1) manually as
5ff9cd35c5f5052cc7a9c4a63759cf8d86a5234b.