[SyncFS] Retry initialization of MetadataDatabase on failure of loading ServiceMetadata

chrome/browser/sync_file_system/drive_backend/metadata_database_unittest.cc

Index: chrome/browser/sync_file_system/drive_backend/metadata_database_unittest.cc
diff --git a/chrome/browser/sync_file_system/drive_backend/metadata_database_unittest.cc b/chrome/browser/sync_file_system/drive_backend/metadata_database_unittest.cc
index 733797a010f35df97620bb34e99d53601162c026..c89f25ad70920f9e5444cb39099675de211cefa8 100644
--- a/chrome/browser/sync_file_system/drive_backend/metadata_database_unittest.cc
+++ b/chrome/browser/sync_file_system/drive_backend/metadata_database_unittest.cc
@@ -641,6 +641,12 @@ TEST_F(MetadataDatabaseTest, InitializationTest_Empty) {
   EXPECT_EQ(SYNC_STATUS_OK, InitializeMetadataDatabase());
   DropDatabase();
   EXPECT_EQ(SYNC_STATUS_OK, InitializeMetadataDatabase());

[nhiroki, 2014/09/03 04:30:06]

This init->drop-init sequence might not make sense when using
|in_memory_env_|...?

[peria, 2014/09/03 09:24:21]

It works well as long as we use |in_memory_env_|.

ref. 
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/leveld...
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/leveld...

[nhiroki, 2014/09/03 09:52:20]

I see. I wrongly assumed |in_memory_env_| is recreated in the sequence. Thanks
for your explanation.

+
+  DropDatabase();
+  scoped_ptr<LevelDBWrapper> db = InitializeLevelDB();
+  db->Put(kServiceMetadataKey, "Unparsable string");
+  db->Commit();
+  EXPECT_EQ(SYNC_STATUS_OK, InitializeMetadataDatabase());
 }
 
 TEST_F(MetadataDatabaseTest, InitializationTest_SimpleTree) {