 Chromium Code Reviews
 Chromium Code Reviews Issue 2182603002:
  Bitrate prober and paced sender improvements  (Closed) 
  Base URL: https://chromium.googlesource.com/external/webrtc.git@master
    
  
    Issue 2182603002:
  Bitrate prober and paced sender improvements  (Closed) 
  Base URL: https://chromium.googlesource.com/external/webrtc.git@master| Index: webrtc/modules/pacing/bitrate_prober_unittest.cc | 
| diff --git a/webrtc/modules/pacing/bitrate_prober_unittest.cc b/webrtc/modules/pacing/bitrate_prober_unittest.cc | 
| index 9e38220e01287a1b4f21e222abfbce5172253ef6..ce63781e6871b01604e3eef4344a5d9bf9f57582 100644 | 
| --- a/webrtc/modules/pacing/bitrate_prober_unittest.cc | 
| +++ b/webrtc/modules/pacing/bitrate_prober_unittest.cc | 
| @@ -65,6 +65,7 @@ TEST(BitrateProberTest, DoesntProbeWithoutRecentPackets) { | 
| prober.OnIncomingPacket(300000, 1000, now_ms); | 
| EXPECT_TRUE(prober.IsProbing()); | 
| EXPECT_EQ(0, prober.TimeUntilNextProbe(now_ms)); | 
| + prober.PacketSent(now_ms, 1000); | 
| 
stefan-webrtc
2016/07/29 07:12:07
Did you add this to test the inactivity threshold?
 
Irfan
2016/08/01 18:29:47
Yes, this is necessary (and makes sense in the flo
 | 
| // Let time pass, no large enough packets put into prober. | 
| now_ms += 6000; | 
| EXPECT_EQ(-1, prober.TimeUntilNextProbe(now_ms)); |