Gather metrics classifying the cause of the TLS fallback.

chrome/browser/extensions/api/socket/tls_socket_unittest.cc

Index: chrome/browser/extensions/api/socket/tls_socket_unittest.cc
diff --git a/chrome/browser/extensions/api/socket/tls_socket_unittest.cc b/chrome/browser/extensions/api/socket/tls_socket_unittest.cc
index adebfbf9f33d471cc65d0ee4679e83c92c03c067..2a478e74e5cb28716d8e36acdd563fba7dd00fa2 100644
--- a/chrome/browser/extensions/api/socket/tls_socket_unittest.cc
+++ b/chrome/browser/extensions/api/socket/tls_socket_unittest.cc
@@ -66,6 +66,7 @@ class MockSSLClientSocket : public net::SSLClientSocket {
   MOCK_CONST_METHOD0(GetUnverifiedServerCertificateChain,
                      scoped_refptr<net::X509Certificate>());
   MOCK_CONST_METHOD0(GetChannelIDService, net::ChannelIDService*());
+  MOCK_CONST_METHOD0(GetSSLFailureState, net::SSLFailureState());

[Ryan Sleevi, 2015/05/14 23:30:20]

Not your fault, but a lot of this API is all "Danger Zone" because it fails to
actually return the bits from the Mock, and thus can cause who knows what kind
of side-effects :)

[davidben, 2015/05/15 18:00:23]

Acknowledged. (I'm assuming there's nothing really to be done here? I could
switch this and most of the rest to concrete no-op implementations.)

   bool IsConnected() const override { return true; }
 
  private: