Use TaskScheduler instead of blocking pool in google_update_metrics_provider_win.cc.

chrome/browser/metrics/google_update_metrics_provider_win.h

Index: chrome/browser/metrics/google_update_metrics_provider_win.h
diff --git a/chrome/browser/metrics/google_update_metrics_provider_win.h b/chrome/browser/metrics/google_update_metrics_provider_win.h
index 171ee7945a70741bb2e22fa6dec9952f08a87615..d59309df21e068630102bbc880b33195d458dd2d 100644
--- a/chrome/browser/metrics/google_update_metrics_provider_win.h
+++ b/chrome/browser/metrics/google_update_metrics_provider_win.h
@@ -50,7 +50,7 @@ class GoogleUpdateMetricsProviderWin : public metrics::MetricsProvider {
   };
 
   // Retrieve the Google Update data on the blocking pool.
-  static GoogleUpdateMetrics GetGoogleUpdateDataOnBlockingPool();
+  static GoogleUpdateMetrics GetGoogleUpdateDataBlocking();

[Alexei Svitkine (slow), 2017/02/03 21:05:16]

Nit: This function name doesn't make sense to me anymore.

Previous name emphasized it was on blocking pool, i.e. where it should be run.
New name just says "Blocking" which I don't think makes sense. Also, comment is
still as before.

Please name it in a way that makes more sense.

 
   // Receives |google_update_metrics| from a blocking pool thread and runs
   // |done_callback|.