in RtcpTransceiverImplTest relax expectation on wait time between reports
If 10ms delayed report is scheduled at 1.9ms (truncated by TaskQueue clock to 1ms) it may run at 11.1ms (truncated to 11ms, i.e. first time it look like 10ms passed). But (test) clock with different time offset may see passed time as 9ms which result in a test failure for a wrong reason. Relaxing period expectation by 1ms should mitigate the issue Bug: webrtc:8945 Change-Id: I902d8af436fc74d4a3a0ad8ffdb5a6d3565adb7d Reviewed-on: https://webrtc-review.googlesource.com/58095 Commit-Queue: Niels Moller <nisse@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22361}
This commit is contained in:

committed by
Commit Bot

parent
8fabab1509
commit
a06f360d5b
@ -181,7 +181,7 @@ TEST(RtcpTransceiverImplTest, PeriodicallySendsPackets) {
|
||||
int64_t time_just_after_2nd_packet_ms = rtc::TimeMillis();
|
||||
|
||||
EXPECT_GE(time_just_after_2nd_packet_ms - time_just_before_1st_packet_ms,
|
||||
config.report_period_ms);
|
||||
config.report_period_ms - 1);
|
||||
|
||||
// Cleanup.
|
||||
rtc::Event done(false, false);
|
||||
@ -226,7 +226,7 @@ TEST(RtcpTransceiverImplTest, SendCompoundPacketDelaysPeriodicSendPackets) {
|
||||
int64_t time_of_last_periodic_packet_ms = rtc::TimeMillis();
|
||||
|
||||
EXPECT_GE(time_of_last_periodic_packet_ms - time_of_non_periodic_packet_ms,
|
||||
config.report_period_ms);
|
||||
config.report_period_ms - 1);
|
||||
|
||||
// Cleanup.
|
||||
rtc::Event done(false, false);
|
||||
|
Reference in New Issue
Block a user