sync: Remove SyncSourceInfo

chrome/browser/sync/profile_sync_service_harness.cc

Index: chrome/browser/sync/profile_sync_service_harness.cc
diff --git a/chrome/browser/sync/profile_sync_service_harness.cc b/chrome/browser/sync/profile_sync_service_harness.cc
index c89df6d886170ddfb4a3eb772de8d94e7a296edc..67aea3109d0921e6cf637b5bdb9cd6788d991c96 100644
--- a/chrome/browser/sync/profile_sync_service_harness.cc
+++ b/chrome/browser/sync/profile_sync_service_harness.cc
@@ -501,9 +501,14 @@ void ProfileSyncServiceHarness::OnSyncCycleCompleted() {
   bool is_notifiable_commit =
       (snap.model_neutral_state().num_successful_commits > 0);
   if (is_notifiable_commit && p2p_invalidation_service_) {
-    const syncer::ObjectIdInvalidationMap& invalidation_map =
-        ModelTypeInvalidationMapToObjectIdInvalidationMap(
-            snap.source().types);
+    syncer::ModelTypeSet model_types =
+        snap.model_neutral_state().commit_request_types;

[tim (not reviewing), 2013/08/01 17:16:38]

Am I correct that we only need commit_request_types for p2p / integration tests?
 Would this be interesting for about:sync?  

[rlarocque, 2013/08/01 21:01:41]

Yep, it's only for tests.  I wish I could have avoided it, but I didn't see any
better way to keep the tests running.
The information might be useful, but I'm not sure where I'd put it.  If we ever
get around to replacing the counters with a concise event log, we might be able
to use it then.

+    syncer::ObjectIdSet ids = ModelTypeSetToObjectIdSet(model_types);
+    syncer::ObjectIdInvalidationMap invalidation_map =
+        syncer::ObjectIdSetToInvalidationMap(
+            ids,
+            syncer::Invalidation::kUnknownVersion,
+            "");
     p2p_invalidation_service_->SendInvalidation(invalidation_map);
   }