Make BW checks > 0 in peerconnection_unittest.cc.
These checks (> 40k) fail on LSan FYI bots and the purpose of them seem
to be that we're getting non-zero BW reported.
R=stefan@webrtc.org
TBR=jiayl@webrtc.org, solenberg@webrtc.org
BUG=3817,chromium:375154
Review URL: https://webrtc-codereview.appspot.com/29479004
git-svn-id: http://webrtc.googlecode.com/svn/trunk/talk@7183 4adac7df-926f-26a2-2b94-8c16560cd09d
diff --git a/app/webrtc/peerconnection_unittest.cc b/app/webrtc/peerconnection_unittest.cc
index 402a796..0d3e426 100644
--- a/app/webrtc/peerconnection_unittest.cc
+++ b/app/webrtc/peerconnection_unittest.cc
@@ -1512,9 +1512,8 @@
LocalP2PTest();
// Run until a non-zero bw is reported.
- EXPECT_TRUE_WAIT(
- receiving_client()->GetAvailableReceivedBandwidthStats() > 40000,
- kMaxWaitForRembMs);
+ EXPECT_TRUE_WAIT(receiving_client()->GetAvailableReceivedBandwidthStats() > 0,
+ kMaxWaitForRembMs);
// Halt video capturers, then run until we have gotten some audio. Following
// REMB should be non-zero.
@@ -1539,9 +1538,8 @@
LocalP2PTest();
// Run until a non-zero bw is reported.
- EXPECT_TRUE_WAIT(
- receiving_client()->GetAvailableReceivedBandwidthStats() > 40000,
- kMaxWaitForRembMs);
+ EXPECT_TRUE_WAIT(receiving_client()->GetAvailableReceivedBandwidthStats() > 0,
+ kMaxWaitForRembMs);
// Halt video capturers, then run until we have gotten some audio. Following
// REMB should be zero.