Remove destruction-only TearDown() methods in Drive related test.

chrome/browser/chromeos/drive/drive_integration_service_unittest.cc

Index: chrome/browser/chromeos/drive/drive_integration_service_unittest.cc
diff --git a/chrome/browser/chromeos/drive/drive_integration_service_unittest.cc b/chrome/browser/chromeos/drive/drive_integration_service_unittest.cc
index db8df9add8541e2242bcad5438037eb00b018c02..9c7812a42b95551e404704d673bd28d378897348 100644
--- a/chrome/browser/chromeos/drive/drive_integration_service_unittest.cc
+++ b/chrome/browser/chromeos/drive/drive_integration_service_unittest.cc
@@ -24,12 +24,6 @@ class DriveIntegrationServiceTest : public testing::Test {
         new DummyFileSystem));
   }
 
-  virtual void TearDown() OVERRIDE {
-    integration_service_.reset();
-    google_apis::test_util::RunBlockingPoolTask();
-    profile_.reset();
-  }
-
  protected:
   content::TestBrowserThreadBundle thread_bundle_;
   scoped_ptr<TestingProfile> profile_;
@@ -40,6 +34,7 @@ TEST_F(DriveIntegrationServiceTest, InitializeAndShutdown) {
   integration_service_->Initialize();
   google_apis::test_util::RunBlockingPoolTask();
   integration_service_->Shutdown();
+  google_apis::test_util::RunBlockingPoolTask();

[hashimoto, 2013/07/03 07:58:47]

Isn't the dtor of BrowserThread is responsible to flush all pending jobs in the
blocking pool?

[kinaba, 2013/07/03 10:06:58]

Done.

 }
 
 }  // namespace drive