Abandon user sign in when policy is retrieved before session started

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index bc394591e16ee5af82652f3173ca98a9879ed251..7c3b96357625fb9ae921ca7190377c80eb3c1cf0 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -15067,6 +15067,12 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="Enterprise.RetrievePolicyResponse"

[emaxx, 2017/04/18 15:03:17]

Would it be useful to have different metrics depending on the policy type (like
user/device/device-local)? They are stored quite differently, and the
implications of errors with each of them are quite different.

[igorcov, 2017/04/20 14:52:29]

Done.

+    enum="RetrievePolicyResponseType">
+  <owner>igorcov@chromium.org</owner>
+  <summary>The response obtained to retrieve policy request.</summary>
+</histogram>
+
 <histogram name="Enterprise.SystemLogPIILeak" enum="SystemLogPIIType">
   <obsolete>
     Deprecated and removed from code as of 01/2016.
@@ -109208,6 +109214,12 @@ from previous Chrome versions.
   <int value="1" label="Cached StyleSheetContents was reused"/>
 </enum>
 
+<enum name="RetrievePolicyResponseType" type="int">
+  <int value="0" label="Success"/>
+  <int value="1" label="Retrieve request issued before session started"/>
+  <int value="2" label="Other type of error on retrieve policy request"/>
+</enum>
+
 <enum name="RevalidationPolicy" type="int">
   <int value="0" label="Use"/>
   <int value="1" label="Revalidate"/>