parse flags in unit tests

Summary: This code has useful logging when turned up high enough (e.g. --v=11). But we need to parse the flags to see it.

Test Plan: trial & error

Reviewed By: yfeldblum@fb.com

Subscribers: enis, folly-diffs@, jsedgwick, yfeldblum, darshan, chalfant

FB internal diff: D1985965

Signature: t1:1985965:1428713065:4607610ec438416fffb5fced1867efa13544eef0

diff --git a/folly/futures/test/main.cpp b/folly/futures/test/main.cpp
index 44a34867c781109731e38a4518f3a11f8a5e8879..457278f6bdf538b64d512762b155ad410a0aa042 100644 (file)
--- a/folly/futures/test/main.cpp
+++ b/folly/futures/test/main.cpp
@@ -15,8 +15,10 @@
  */
 
 #include <gtest/gtest.h>
+#include <gflags/gflags.h>
 
 int main(int argc, char** argv) {
   ::testing::InitGoogleTest(&argc, argv);
+  ::google::ParseCommandLineFlags(&argc, &argv, true);
   return RUN_ALL_TESTS();
 }