Chromium Code Reviews| Index: webrtc/video/video_send_stream_tests.cc |
| diff --git a/webrtc/video/video_send_stream_tests.cc b/webrtc/video/video_send_stream_tests.cc |
| index 623cd34ac5e8860f7b9e6666172f5a082134ffa7..3da62b9becf1d04e0bd6c9633d50549f88791eda 100644 |
| --- a/webrtc/video/video_send_stream_tests.cc |
| +++ b/webrtc/video/video_send_stream_tests.cc |
| @@ -136,8 +136,16 @@ TEST_F(VideoSendStreamTest, SupportsAbsoluteSendTime) { |
| EXPECT_FALSE(header.extension.hasTransmissionTimeOffset); |
| EXPECT_TRUE(header.extension.hasAbsoluteSendTime); |
| EXPECT_EQ(header.extension.transmissionTimeOffset, 0); |
| - EXPECT_GT(header.extension.absoluteSendTime, 0u); |
| - observation_complete_.Set(); |
| + if (header.extension.absoluteSendTime != 0) { |
| + // Wait for at least one packet with a non-zero send time. The send time |
| + // is a 16-bit value derived from the system clock, and it is valid |
| + // for a packet to have a zero send time. To tell that from an |
| + // unpopulated value we'll wait for a packet with non-zero send time. |
| + observation_complete_.Set(); |
| + } else { |
| + LOG(LS_WARNING) << "Got a packet with zero absSendTime; waiting for" |
|
pbos-webrtc
2016/09/01 23:44:51
absoluteSendTime, waiting
+ formatting after that
|
| + " another packet..."; |
| + } |
| return SEND_PACKET; |
| } |