SERVER-19000 Fix thread_pool_test.

While joining a ThreadPool, the value of the "numThreads" stats value is locked
at the number of threads that existed when the join operation began, even if one
or more of those threads have since exited. This is because the numThreads value
is computed as the number of threads in the _threads container, which are the
threads that will be joined individually during a pool join operation.

As such, it is not correct to make assertions about the value of numThreads
while ThreadPool::join is running, as it is in DestructionDuringDoubleJoins.

1 files changed, 0 insertions, 1 deletions

diff --git a/src/mongo/util/concurrency/thread_pool_test.cpp b/src/mongo/util/concurrency/thread_pool_test.cpp
index 74881f0508e..3f8f0ef07e8 100644
--- a/src/mongo/util/concurrency/thread_pool_test.cpp
+++ b/src/mongo/util/concurrency/thread_pool_test.cpp
@@ -274,7 +274,6 @@ DEATH_TEST(ThreadPoolTest,
     while ((stats = pool->getStats()).numIdleThreads != 0U) {
         sleepmillis(50);
     }
-    ASSERT_EQ(1U, stats.numThreads);
     ASSERT_EQ(0U, stats.numPendingTasks);
     pool.reset();
     lk.unlock();