From 01ed7b20aec82163defd3e370e82ee9a83fbb951 Mon Sep 17 00:00:00 2001 From: Konstantin Varlamov Date: Wed, 9 May 2018 12:01:20 -0400 Subject: Firestore C++: in AsyncQueue, use steady_clock instead of system_clock. (#1246) This should prevent weird bugs due to system time readjustments. Because operations are scheduled relative to now, the fact that the resulting timepoint isn't in Unix epoch shouldn't matter. --- Firestore/core/test/firebase/firestore/util/async_tests_util.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Firestore/core/test') diff --git a/Firestore/core/test/firebase/firestore/util/async_tests_util.h b/Firestore/core/test/firebase/firestore/util/async_tests_util.h index 422745b..f953d66 100644 --- a/Firestore/core/test/firebase/firestore/util/async_tests_util.h +++ b/Firestore/core/test/firebase/firestore/util/async_tests_util.h @@ -27,11 +27,11 @@ namespace firebase { namespace firestore { namespace util { -inline std::chrono::time_point now() { return std::chrono::time_point_cast( - std::chrono::system_clock::now()); + std::chrono::steady_clock::now()); } constexpr auto kTimeout = std::chrono::seconds(5); -- cgit v1.2.3