commit | b9ca78e9d1181564c99082dec04c6377ef73e405 | [log] [tgz] |
---|---|---|
author | solenberg <solenberg@webrtc.org> | Wed Feb 22 15:07:04 2017 |
committer | Commit bot <commit-bot@chromium.org> | Wed Feb 22 15:07:04 2017 |
tree | 6f837be6a0bdc7b0611df24aee89f0c6787042b7 | |
parent | ea6f6075a480a6276f362b764ca25efecd4c7deb [diff] |
Fix flaky test WebRtcMediaRecorderTest.PeerConnection A previous CL changed from logging to DCHECKing when setting minimum playout delay on a VoE channel: https://codereview.webrtc.org/2452163004/ I thought it safe at the time, since the input parameter range is capped, but apparently I didn't dig deep enough, as ultimately a failure may be returned for other reasons: https://chromium.googlesource.com/external/webrtc/+/master/webrtc/modules/audio_coding/neteq/delay_manager.cc#381 Thus, reverting to old behavior. BUG=694373 Review-Url: https://codereview.webrtc.org/2704933008 Cr-Original-Commit-Position: refs/heads/master@{#16775} Cr-Mirrored-From: https://chromium.googlesource.com/external/webrtc Cr-Mirrored-Commit: 0335e6c4bfa9a3254a392c003344c71238ee832f