For unit tests, track additions to AtExitManager and warn.

content/test/unittest_test_suite.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/public/test/unittest_test_suite.h"
 
 #include "base/logging.h"
 #include "base/test/test_suite.h"
 #include "third_party/WebKit/Source/WebKit/chromium/public/WebKit.h"
 #include "third_party/WebKit/Source/WebKit/chromium/public/platform/WebKitPlatformSupport.h"
@@ skipping 23 matching lines @@
   DCHECK(test_suite);
   webkit_platform_support_.reset(new UnitTestWebKitPlatformSupport);
   WebKit::initialize(webkit_platform_support_.get());
 }
 
 UnitTestTestSuite::~UnitTestTestSuite() {
   WebKit::shutdown();
 }
 
 int UnitTestTestSuite::Run() {
+  test_suite_->WatchAtExitManager();

[Paweł Hajdan Jr., 2012/06/20 07:47:13]

This should always be run, for all test suites (make the suite in base/ do
that).

[Scott Byer, 2012/06/21 00:05:41]

I was trying to be conservative and not spew warnings all over the place - I had
it there to begin with.

I've fixed it so just browser_tests and interactive_ui_tests don't check since
those tests get run in a sub-process, adding exit manager callbacks / using
singletons seems like something they should be able to do.

content_unittests seems to have the warning fire on an unusually large number of
tests, I'm going to look into that. But it doesn't seem unmanageable.

   return test_suite_->Run();
 }
 
 }  // namespace content