Always expect certificates in QuicChromiumClientSession::CanPool

net/quic/quic_network_transaction_unittest.cc

Index: net/quic/quic_network_transaction_unittest.cc
diff --git a/net/quic/quic_network_transaction_unittest.cc b/net/quic/quic_network_transaction_unittest.cc
index 22ad48ccbbc3389d2b3ff8d069bf4118c9766906..0d3a4b36d78cd4f40b84efdecc93763fb7a83ced 100644
--- a/net/quic/quic_network_transaction_unittest.cc
+++ b/net/quic/quic_network_transaction_unittest.cc
@@ -209,6 +209,7 @@ class QuicNetworkTransactionTest
     verify_details_.cert_verify_result.verified_cert = cert;
     verify_details_.cert_verify_result.is_issued_by_known_root = true;
     crypto_client_stream_factory_.AddProofVerifyDetails(&verify_details_);
+    crypto_client_stream_factory_.AddProofVerifyDetails(&verify_details_);

[Zhongyi Shi, 2015/12/30 22:55:31]

Instead of adding two ProofVerifyDetailsChromium here, is that better to leave
as it is and add ProofVerifyDetailsChromium in the tests when needed?

Or it might be better than we never insert ProofVerifyDetailsChromium in the
cxtor but do that in the test when needed? Some of our test don't require cert
at all. 

[Ryan Hamilton, 2015/12/30 23:21:12]

Done. It's just one test.
I thought about that, but it seemed like it was more hassle than it was worth as
it 
would just add noise to all the tests.

   }
 
   void SetUp() override {