For unit tests, track additions to AtExitManager and warn.

content/test/unittest_test_suite.cc

Index: content/test/unittest_test_suite.cc
diff --git a/content/test/unittest_test_suite.cc b/content/test/unittest_test_suite.cc
index 85597d51ae51fdd53fb2eb501213e8c722ecadd1..ebf1f8966f04dd3e1123d2d51ee9e370016d37b6 100644
--- a/content/test/unittest_test_suite.cc
+++ b/content/test/unittest_test_suite.cc
@@ -41,6 +41,7 @@ UnitTestTestSuite::~UnitTestTestSuite() {
 }
 
 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();
 }