summaryrefslogtreecommitdiff
path: root/src/mongo/util
diff options
context:
space:
mode:
authorJason Carey <jcarey@argv.me>2018-05-21 12:34:25 -0400
committerJason Carey <jcarey@argv.me>2018-09-05 16:04:33 -0400
commit7d58026a631baba1c3b62d071238d8d56bd0302a (patch)
tree0c46ef5a83dc5e3ac6de10e1ab0da9aaaf1bfe46 /src/mongo/util
parentf1193a0eff320fc8b5b8c54db455af0077ad9855 (diff)
downloadmongo-7d58026a631baba1c3b62d071238d8d56bd0302a.tar.gz
SERVER-35123 Fix periodic_runner_impl_test
The periodic runner impl starts jobs immediately, rather than waiting for some time to pass on their first run. That's fine, and the correct behavior, but the unittest assumes that doesn't happen. The unittest needs to be updated to reflect realty. (cherry picked from commit b0c577146568c6e1d51b2db29bf21f4d87e93c85)
Diffstat (limited to 'src/mongo/util')
-rw-r--r--src/mongo/util/periodic_runner_impl_test.cpp6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/mongo/util/periodic_runner_impl_test.cpp b/src/mongo/util/periodic_runner_impl_test.cpp
index 210871ea4db..cd2937c50e1 100644
--- a/src/mongo/util/periodic_runner_impl_test.cpp
+++ b/src/mongo/util/periodic_runner_impl_test.cpp
@@ -97,12 +97,6 @@ TEST_F(PeriodicRunnerImplTest, OneJobTest) {
runner().scheduleJob(std::move(job));
- // Ensure nothing happens until we fastForward
- {
- stdx::unique_lock<stdx::mutex> lk(mutex);
- ASSERT_EQ(count, 0);
- }
-
// Fast forward ten times, we should run all ten times.
for (int i = 0; i < 10; i++) {
clockSource().advance(interval);