Hack clock_unittest fix for parallel execution.
It's a bad idea to depend on timing constraints in unit tests, but moving this from 5 -> 100 ms should allow it to fail only very rarely. TBR=pbos@webrtc.org Review URL: https://webrtc-codereview.appspot.com/35659004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@7999 4adac7df-926f-26a2-2b94-8c16560cd09d
This commit is contained in:
parent
c37e72e890
commit
a37bf2c4fe
@ -22,6 +22,7 @@ TEST(ClockTest, NtpTime) {
|
||||
int64_t milliseconds = clock->CurrentNtpInMilliseconds();
|
||||
EXPECT_GT(milliseconds / 1000, kNtpJan1970);
|
||||
EXPECT_GE(milliseconds, Clock::NtpToMs(seconds, fractions));
|
||||
EXPECT_NEAR(milliseconds, Clock::NtpToMs(seconds, fractions), 5);
|
||||
EXPECT_NEAR(milliseconds, Clock::NtpToMs(seconds, fractions), 100);
|
||||
}
|
||||
|
||||
} // namespace webrtc
|
||||
|
Loading…
Reference in New Issue
Block a user