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

chrome/browser/chromeos/drive/change_list_processor_unittest.cc

Index: chrome/browser/chromeos/drive/change_list_processor_unittest.cc
diff --git a/chrome/browser/chromeos/drive/change_list_processor_unittest.cc b/chrome/browser/chromeos/drive/change_list_processor_unittest.cc
index 92ca34f5de6609d6a92ef900aa4a8e3bad9f95f7..14955636ad45726db6141500c65f46873d663564 100644
--- a/chrome/browser/chromeos/drive/change_list_processor_unittest.cc
+++ b/chrome/browser/chromeos/drive/change_list_processor_unittest.cc
@@ -51,10 +51,6 @@ class ChangeListProcessorTest : public testing::Test {
     ASSERT_EQ(FILE_ERROR_OK, metadata_->Initialize());
   }
 
-  virtual void TearDown() OVERRIDE {
-    metadata_.reset();
-  }
-
   // Parses a json file at |test_data_path| relative to Chrome test directory
   // into a ScopedVector<drive::internal::ChangeList>.
   ScopedVector<ChangeList> ParseChangeList(const std::string& test_data_path) {