|
|
|||
Issue descriptionFix ProofTest.Verify and enable it. [ RUN ] ProofTest.Verify ** Message: Skipping credential gecc because its status is NEED_KEY ../../net/quic/crypto/proof_test.cc:126: Failure Value of: source->GetProof(server_ip, hostname, server_config, false , &first_certs, &first_signature) Actual: false Expected: true [ FAILED ] ProofTest.Verify (1274 ms) , Apr 25 2018Project Member
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot , Dec 15Project MemberThe following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b28c476f724774d786a63a9e9e37e2ed925240c1 commit b28c476f724774d786a63a9e9e37e2ed925240c1 Author: David Benjamin <davidben@chromium.org> Date: Sat Dec 15 04:47:15 2018 Enable ProofTest.Verify. Inspired by pkasting's email, I noticed this... It seems to work these days. Maybe the BoringSSL switch? The bug has some error coming out of NSS. Bug: 514468 Change-Id: Ic0ba0af9b19019fea230e9ca171e2daf09fccbb2 Reviewed-on: https://chromium-review.googlesource.com/c/1378817 Reviewed-by: Ryan Hamilton <rch@chromium.org> Commit-Queue: Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#616955} [modify] https://crrev.com/b28c476f724774d786a63a9e9e37e2ed925240c1/net/quic/crypto/proof_test_chromium.cc , Dec 17
|
|||
►
Sign in to add a comment |
|||
Comment 1 by rtenneti@chromium.org, Apr 24 2017
Status: Available (was: Assigned)