[Sync] InvalidationService shouldn't CHECK when registering ObjectId for more than one handler

chrome/browser/policy/cloud/remote_commands_invalidator.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/policy/cloud/remote_commands_invalidator.h"
 
 #include <string>
 
 #include "base/logging.h"
 #include "components/invalidation/invalidation.h"
@@ skipping 120 matching lines @@
     invalidation_service_->RegisterInvalidationHandler(this);
     is_registered_ = true;
   }
 
   object_id_ = object_id;
   UpdateInvalidationsEnabled();
 
   // Update registration with the invalidation service.
   syncer::ObjectIdSet ids;
   ids.insert(object_id);
-  invalidation_service_->UpdateRegisteredInvalidationIds(this, ids);
+  CHECK(invalidation_service_->UpdateRegisteredInvalidationIds(this, ids));

[bartfab (slow), 2015/05/19 10:44:42]

Nit: As in the other file, LOG(ERROR) would be sufficient here.

 }
 
 void RemoteCommandsInvalidator::Unregister() {
   if (is_registered_) {
-    invalidation_service_->UpdateRegisteredInvalidationIds(
-        this, syncer::ObjectIdSet());
+    CHECK(invalidation_service_->UpdateRegisteredInvalidationIds(
+        this, syncer::ObjectIdSet()));
     invalidation_service_->UnregisterInvalidationHandler(this);
     is_registered_ = false;
     UpdateInvalidationsEnabled();
   }
 }
 
 void RemoteCommandsInvalidator::UpdateInvalidationsEnabled() {
   invalidations_enabled_ = invalidation_service_enabled_ && is_registered_;
 }
 
 }  // namespace policy