| commit | 5865f48dcb5f14346876428fd0f3a66473839b0c | [log] [tgz] |
|---|---|---|
| author | kjellander <kjellander@webrtc.org> | Thu Sep 08 10:52:38 2016 -0700 |
| committer | Commit bot <commit-bot@chromium.org> | Thu Sep 08 17:52:41 2016 +0000 |
| tree | fd47e7e452bb53463de7247583ceb3d3b0ddebde | |
| parent | 906f4030882ad6b7f31658e43a15e6165f3431d0 [diff] |
Revert of Separating video settings in VideoQualityTest. (patchset #2 id:20001 of https://codereview.webrtc.org/2312613003/ ) Reason for revert: Breaks webrtc_perf_tests on Windows, Mac and Linux (that test don't run on trybots): https://build.chromium.org/p/client.webrtc/builders/Linux64%20Release%20%5Blarge%20tests%5D/builds/8841/steps/webrtc_perf_tests/logs/stdio Example: [ RUN ] FullStackTest.ForemanCifWithoutPacketLossVp9 # Fatal error in ../../webrtc/video/video_quality_test.cc, line 1056 # last system error: 34 # Check failed: !params_.audio.enabled Original issue's description: > Separating video settings in VideoQualityTest. > > This is a simple refactoring of VideoQualityTest. It will help in adding audio related settings to VideoQualityTest. > > BUG= > > Committed: https://crrev.com/f07fb0013164bdb031dcc88dc83365a27643b2d9 > Cr-Commit-Position: refs/heads/master@{#14139} TBR=stefan@webrtc.org,minyue@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review-Url: https://codereview.webrtc.org/2325723002 Cr-Commit-Position: refs/heads/master@{#14142}
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.