Don't reset the database when there was an I/O error.

content/browser/indexed_db/indexed_db_cleanup_on_io_error_unittest.cc

Index: content/browser/indexed_db/indexed_db_cleanup_on_io_error_unittest.cc
diff --git a/content/browser/indexed_db/indexed_db_cleanup_on_io_error_unittest.cc b/content/browser/indexed_db/indexed_db_cleanup_on_io_error_unittest.cc
index 6b60a4f9291a2c1b2547823afb15516133cbbab0..08ffa36278d61789979edf46eed1b2ced29e58ef 100644
--- a/content/browser/indexed_db/indexed_db_cleanup_on_io_error_unittest.cc
+++ b/content/browser/indexed_db/indexed_db_cleanup_on_io_error_unittest.cc
@@ -138,7 +138,7 @@ TEST(IndexedDBNonRecoverableIOErrorTest, NuancedCleanupTest) {
                                   &disk_full,
                                   &mock_leveldb_factory2);
 
-  MockErrorLevelDBFactory<int> mock_leveldb_factory3(EIO, true);
+  MockErrorLevelDBFactory<int> mock_leveldb_factory3(EIO, false);

[jsbell, 2013/10/04 23:32:33]

Do we have any cases where DestroyLevelDB() is called now? If not, should we
simplify the fixture?

[dgrogan, 2013/10/05 01:06:16]

Good point. I added a TODO. Even though it's just like 10 lines of code, I don't
want to delete it because I have an inkling that we're going to turn deleting
back on for a subset of I/O errors in a near-future release.

   scoped_refptr<IndexedDBBackingStore> backing_store3 =
       IndexedDBBackingStore::Open(origin_identifier,
                                   path,
@@ -148,7 +148,7 @@ TEST(IndexedDBNonRecoverableIOErrorTest, NuancedCleanupTest) {
                                   &mock_leveldb_factory3);
 
   MockErrorLevelDBFactory<base::PlatformFileError> mock_leveldb_factory4(
-      base::PLATFORM_FILE_ERROR_FAILED, true);
+      base::PLATFORM_FILE_ERROR_FAILED, false);
   scoped_refptr<IndexedDBBackingStore> backing_store4 =
       IndexedDBBackingStore::Open(origin_identifier,
                                   path,