[Retry][SyncFS] Implement LargestKnownChangeID handling

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 27da341017e981dd0c37721016d4e9dd6b3e031c..070ef6ee976e29d5f238b7f8a6df42439d7900f7 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
@@ -401,6 +401,10 @@ class MetadataDatabaseTest : public testing::Test {
     details->set_change_id(++current_change_id_);
   }
 
+  void ApplyNoopChangeToMetadata(FileMetadata* file) {
+    file->mutable_details()->set_change_id(++current_change_id_);
+  }
+
   void PushToChangeList(scoped_ptr<google_apis::ChangeResource> change,
                         ScopedVector<google_apis::ChangeResource>* changes) {
     changes->push_back(change.release());
@@ -748,6 +752,7 @@ TEST_F(MetadataDatabaseTest, UpdateByChangeListTest) {
   ApplyReorganizeChangeToMetadata(folder.metadata.file_id(),
                                   &reorganized_file.metadata);
   ApplyContentChangeToMetadata(&updated_file.metadata);
+  ApplyNoopChangeToMetadata(&noop_file.metadata);

[kinuko, 2013/11/18 06:57:11]

Care to add a comment why we need it?

[tzik, 2013/11/18 07:17:13]

Done.

 
   ScopedVector<google_apis::ChangeResource> changes;
   PushToChangeList(