From a37bf2c4fe256527a8f926fa845a29ca67877653 Mon Sep 17 00:00:00 2001 From: "andrew@webrtc.org" Date: Mon, 5 Jan 2015 19:08:58 +0000 Subject: [PATCH] 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 --- webrtc/system_wrappers/source/clock_unittest.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/webrtc/system_wrappers/source/clock_unittest.cc b/webrtc/system_wrappers/source/clock_unittest.cc index 71969edcd0..8672d3966e 100644 --- a/webrtc/system_wrappers/source/clock_unittest.cc +++ b/webrtc/system_wrappers/source/clock_unittest.cc @@ -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