The bit rate target for ramp down in was set equal to the simulated
capacity. Expected behavior of an estimator is to achieve an estimate
near the true value but not always the exact value. Adding a margin
allows from noise in the measurement while still testing for the desired
behavor.
Bug: webrtc:8878
Change-Id: I18fb6c9704bf08e58ee08ce6c85abee2eaa08356
Reviewed-on: https://webrtc-review.googlesource.com/57080
Reviewed-by: Niels Moller <nisse@webrtc.org>
Reviewed-by: Stefan Holmer <stefan@webrtc.org>
Commit-Queue: Sebastian Jansson <srte@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#22171}
Due to flakiness. See bug.
TBR=stefan@webrtc.org
Bug: webrtc:8878
Change-Id: Iece487ad9883fbe6209d25291fb70bb52c8afbd3
Reviewed-on: https://webrtc-review.googlesource.com/54601
Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#22059}
For the RampUpTest.UpDownUpAbsSendTimeSimulcastRedRtx and
RampUpTest.UpDownUpTransportSequenceNumberRtx [1,2], the generated metric names
are the same:
- ramp_up_down_up_3streams_rtx.first_rampup
- ramp_up_down_up_3streams_rtx.second_rampup
- ramp_up_down_up_3streams_rtx.rampdown
So only one of the two tests (whichever ran last) has its metrics reported to
the perf dashboard, while the others has its metrics ignored.
[1] https://webrtc.googlesource.com/src/+/master/call/rampup_tests.cc#571
[2] https://webrtc.googlesource.com/src/+/master/call/rampup_tests.cc#579
Bug: webrtc:8691
Change-Id: I632dfe32d3b4729f1b0233c44d03c2894ee8c027
Reviewed-on: https://webrtc-review.googlesource.com/36941
Reviewed-by: Patrik Höglund <phoglund@webrtc.org>
Reviewed-by: Henrik Andreassson <henrika@webrtc.org>
Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#21499}
It's been disabled on Linux and Mac already, but appears to be flaky
regardless of platform; flakes have been observed on Android and
Windows as well.
TBR=stefan@webrtc.org
NOTRY=True
Bug: webrtc:7919
Change-Id: I193f6836fa3ad3928ed7ac05ade4504fa5e37442
Reviewed-on: https://webrtc-review.googlesource.com/8240
Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org>
Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#20230}
Replaced with scalars ulpfec_payload_type and red_payload_type.
In particular, ulpfec.red_rtx_payload_type, which duplicated info in
rtx_associated_payload_types, is deleted. This is a followup to cl
https://codereview.webrtc.org/3012963002.
BUG=webrtc:7135
Review-Url: https://codereview.webrtc.org/3019453002
Cr-Commit-Position: refs/heads/master@{#19965}
In https://webrtc-review.googlesource.com/c/src/+/1560 we moved WebRTC
from src/webrtc to src/ (in order to preserve an healthy git history).
This CL takes care of fixing header guards, #include paths, etc...
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
TBR=tommi@webrtc.org
Bug: chromium:611808
Change-Id: Iea91618212bee0af16aa3f05071eab8f93706578
Reviewed-on: https://webrtc-review.googlesource.com/1561
Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
Reviewed-by: Henrik Kjellander <kjellander@webrtc.org>
Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#19846}
In order to eliminate the WebRTC Subtree mirror in Chromium,
WebRTC is moving the content of the src/webrtc directory up
to the src/ directory.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
TBR=tommi@webrtc.org
Bug: chromium:611808
Change-Id: Iac59c5b51b950f174119565bac87955a7994bc38
Reviewed-on: https://webrtc-review.googlesource.com/1560
Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org>
Reviewed-by: Henrik Kjellander <kjellander@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#19845}
