Make Blacklist::IsBlacklist asynchronous (it will need to be for safe

chrome/browser/protector/protected_prefs_watcher_unittest.cc

Index: chrome/browser/protector/protected_prefs_watcher_unittest.cc
diff --git a/chrome/browser/protector/protected_prefs_watcher_unittest.cc b/chrome/browser/protector/protected_prefs_watcher_unittest.cc
index f69b0431701ca56050d2f06fcacf865138d95b7f..f67d7f7de07973a5cea2c71eb34a43ae9408ba11 100644
--- a/chrome/browser/protector/protected_prefs_watcher_unittest.cc
+++ b/chrome/browser/protector/protected_prefs_watcher_unittest.cc
@@ -132,9 +132,7 @@ TEST_F(ProtectedPrefsWatcherTest, ExtensionPrefChange) {
   EXPECT_FALSE(IsSignatureValid());
 
   // Blacklisting the extension does update the backup and signature.
-  std::set<std::string> blacklist;
-  blacklist.insert(sample_id);
-  extension_prefs->UpdateBlacklist(blacklist);
+  extension_prefs->SetExtensionBlacklisted(sample_id, true);
 
   EXPECT_TRUE(IsSignatureValid());

[not at google - send to devlin, 2012/12/03 21:27:23]

@ivankr this check is failing. Do you know what it's testing, and perhaps,
what's making it fail?

[Ivan Korotkov, 2012/12/04 12:16:20]

ProtectedPrefsWatcher maintains a copy of installed (non-blacklisted) extension
IDs and watches for its updates. Looks like some expectations it relied upon
changed. Feel free to disable the test. It's not enabled by defaylt and we're
soon going to remove this code altogether anyway.

 }