CertVerifyProcTest.PublicKeyHashes and TestKnownRoot net_unittests are failing on Windows,Mac and Precise64 official.desktop builders. |
|||
Issue descriptionLink to builders : https://uberchromegw.corp.google.com/i/official.desktop/builders/win/builds/670 https://uberchromegw.corp.google.com/i/official.desktop/builders/mac64/builds/668 https://uberchromegw.corp.google.com/i/official.desktop/builders/precise64/builds/672 Error log : CertVerifyProcTest.TestKnownRoot (run #1): [ RUN ] CertVerifyProcTest.TestKnownRoot c:uild\slave\winuild\src et\cert\cert_verify_proc_unittest.cc(690): error: Value of: error Actual: -201 Expected: OK Which is: 0 [ FAILED ] CertVerifyProcTest.TestKnownRoot (63 ms) CertVerifyProcTest.PublicKeyHashes (run #1): [ RUN ] CertVerifyProcTest.PublicKeyHashes c:uild\slave\winuild\src et\cert\cert_verify_proc_unittest.cc(718): error: Value of: error Actual: -201 Expected: OK Which is: 0 [ FAILED ] CertVerifyProcTest.PublicKeyHashes (0 ms) Suspecting Cl : https://chromium.googlesource.com/chromium/src/+/f8907f402e6141d88721bb4b4307c8fe8f283c5e
,
May 11 2016
One of the downstream official test bots running on M50 failed these two tests yesterday. Can this fix be cherry-picked to M50/M51 to fix the bots?
,
May 20 2016
Not seeing CertVerifyProcTest.PublicKeyHashes and TestKnownRoot net_unittests failing lately on all platforms(Windows, mac and Linux) hence marking the bug as Fixed(Kind of since the Cl in bug report has disabled the failing tests) |
|||
►
Sign in to add a comment |
|||
Comment 1 by jyqu...@chromium.org
, May 10 2016