From af581fbe42659d1ca51a05fde6743ec83998f11b Mon Sep 17 00:00:00 2001
From: James Sedgwick <jsedgwick@fb.com>
Date: Wed, 17 Dec 2014 15:57:16 -0800
Subject: [PATCH] stabilize IOFuturePool test

Summary: see attached task. concurrency is hard.

Test Plan: stress ran the hell out of it, induced failures before, can't after

Reviewed By: hans@fb.com

Subscribers: fugalh, folly-diffs@

FB internal diff: D1746879

Tasks: 5589311

Signature: t1:1746879:1418860467:0ec3f51a398eee8a836532770682a4c58758ce93
---
 .../wangle/concurrent/test/ThreadPoolExecutorTest.cpp           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/folly/experimental/wangle/concurrent/test/ThreadPoolExecutorTest.cpp b/folly/experimental/wangle/concurrent/test/ThreadPoolExecutorTest.cpp
index 9898d40e..3e431073 100644
--- a/folly/experimental/wangle/concurrent/test/ThreadPoolExecutorTest.cpp
+++ b/folly/experimental/wangle/concurrent/test/ThreadPoolExecutorTest.cpp
@@ -242,7 +242,7 @@ TEST(ThreadPoolExecutorTest, IOExpiration) {
 template <typename TPE>
 static void futureExecutor() {
   FutureExecutor<TPE> fe(2);
-  int c = 0;
+  std::atomic<int> c{0};
   fe.addFuture([] () { return makeFuture<int>(42); }).then(
     [&] (Try<int>&& t) {
       c++;
-- 
2.34.1