Make ResolveErrorInfo available from ClientSocketHandle.

A follow-up cl will pipe this information through to NavigationHandle.

Bug: 1016325
Change-Id: I9b5ed84f84029a239edda75b7fd3a2acfdf13c44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1911079
Commit-Queue: Katharine Daly <[email protected]>
Reviewed-by: Matt Menke <[email protected]>
Cr-Commit-Position: refs/heads/master@{#725121}
diff --git a/net/socket/client_socket_pool_base_unittest.cc b/net/socket/client_socket_pool_base_unittest.cc
index 6d7ee44..147b766 100644
--- a/net/socket/client_socket_pool_base_unittest.cc
+++ b/net/socket/client_socket_pool_base_unittest.cc
@@ -34,6 +34,7 @@
 #include "net/base/proxy_server.h"
 #include "net/base/request_priority.h"
 #include "net/base/test_completion_callback.h"
+#include "net/dns/public/resolve_error_info.h"
 #include "net/http/http_response_headers.h"
 #include "net/http/http_response_info.h"
 #include "net/log/net_log.h"
@@ -355,6 +356,10 @@
     return has_established_connection_;
   }
 
+  ResolveErrorInfo GetResolveErrorInfo() const override {
+    return ResolveErrorInfo(OK);
+  }
+
   bool IsSSLError() const override { return store_additional_error_state_; }
 
   scoped_refptr<SSLCertRequestInfo> GetCertRequestInfo() override {