| commit | fd8d2654d704afa80c2fcecff5f3092c381ed249 | [log] [tgz] |
|---|---|---|
| author | brandtr <brandtr@webrtc.org> | Mon Feb 06 06:19:51 2017 -0800 |
| committer | Commit bot <commit-bot@chromium.org> | Mon Feb 06 14:19:51 2017 +0000 |
| tree | ed8221a2fc8948cb9be30938df25e224e54fb7f6 | |
| parent | d40b0f39e08bf0e4d7427bf73b4e3f86bbeb34be [diff] |
Revert of Improve and re-enable FEC end-to-end tests. (patchset #3 id:40001 of https://codereview.webrtc.org/2675573004/ ) Reason for revert: Ulpfec tests are still flaky on buildbots. Original issue's description: > Improve and re-enable FEC end-to-end tests. > > These tests got flaky under the new jitter buffer. > > Enhancements: > - Use send-side BWE. > - Let BWE ramp up before applying packet loss. > - Improve packet loss simulation for ULPFEC. > - Add delay to fake network pipe for FlexFEC. > (Not added for ULPFEC, since this makes those flaky...?) > - Add FlexFEC+NACK test, using RTX instead of "raw retransmits". > - Tighter checks of received packets' payload types and SSRCs. > > TESTED= > $ ninja -C out/Debug video_engine_tests && third_party/gtest-parallel/gtest-parallel -r 1000 out/Debug/video_engine_tests --gtest_filter="*EndToEnd*Ulpfec*:*EndToEnd*Flexfec*" > ninja: Entering directory `out/Debug' > ninja: no work to do. > [12000/12000] TestWithNewVideoJitterBuffer/EndToEndTest.RecoversWithFlexfecAndNack/1 (14935 ms) > > BUG=webrtc:7047 > > Review-Url: https://codereview.webrtc.org/2675573004 > Cr-Commit-Position: refs/heads/master@{#16449} > Committed: https://chromium.googlesource.com/external/webrtc/+/d40b0f39e08bf0e4d7427bf73b4e3f86bbeb34be TBR=stefan@webrtc.org,nisse@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:7047 Review-Url: https://codereview.webrtc.org/2672373002 Cr-Commit-Position: refs/heads/master@{#16450}
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.