commit | 4e52386339e6f872c98df7786b7661bf90b2b58b | [log] [tgz] |
---|---|---|
author | brandtr <brandtr@webrtc.org> | Tue Oct 18 23:50:45 2016 -0700 |
committer | Commit bot <commit-bot@chromium.org> | Wed Oct 19 06:50:53 2016 +0000 |
tree | 7f0b1db9f43872e411b1116157daaf5d3fad7068 | |
parent | 249beee124254cd175622a8b9261a2cfa24cad9b [diff] |
Reland of Add path for recovered packets from internal::Call to RtpStreamReceiver. (patchset #1 id:1 of https://codereview.webrtc.org/2427733002/ ) Reason for revert: Flaky test has been fixed. Original issue's description: > Revert of Add path for recovered packets from internal::Call to RtpStreamReceiver. (patchset #2 id:60001 of https://codereview.webrtc.org/2390823009/ ) > > Reason for revert: > Speculative revert as it may be the cause of the DrMemory test failure: > https://build.chromium.org/p/client.webrtc/builders/Win%20DrMemory%20Full/builds/5115 > > Original issue's description: > > Add path for recovered packets from internal::Call to RtpStreamReceiver. > > > > When the FlexfecReceiver recovers media packets, it inserts these into > > internal::Call, which then distributes them to the appropriate > > VideoReceiveStream/RtpStreamReceiver. > > > > BUG=webrtc:5654 > > > > Committed: https://crrev.com/9c4b4b47f4325b48e1856566a30983f9e4e30dd0 > > Cr-Commit-Position: refs/heads/master@{#14642} > > TBR=stefan@webrtc.org,brandtr@webrtc.org > # Skipping CQ checks because original CL landed less than 1 days ago. > NOPRESUBMIT=true > NOTREECHECKS=true > NOTRY=true > BUG=webrtc:5654 > > Committed: https://crrev.com/862d74d0176fa762b3c96cf20bd36f27e7001a47 > Cr-Commit-Position: refs/heads/master@{#14652} TBR=stefan@webrtc.org,honghaiz@webrtc.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG=webrtc:5654 Review-Url: https://codereview.webrtc.org/2428303004 Cr-Commit-Position: refs/heads/master@{#14677}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.