Summary: | www-client/chromium-28.0.1500.52 fails test CertVerifyProcTest.EVVerification | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus Walter <gentoo> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
www-client:chromium-28.0.1500.52:20130624-182611.log.bz2
emerge --info |
Created attachment 351842 [details]
emerge --info
Pretty sure this has been fixed upstream. + 17 Jul 2013; Mike Gilbert <floppym@gentoo.org> chromium-28.0.1500.71.ebuild, + chromium-28.0.1500.89.ebuild: + Skip CertVerifyProcTest.EVVerification, bug 474642. (In reply to Mike Gilbert from comment #2) > Pretty sure this has been fixed upstream. Indeed. :) |
Created attachment 351840 [details] www-client:chromium-28.0.1500.52:20130624-182611.log.bz2 On my hardened ~amd64 machine with gcc-4.8.1 I see the following test failure for chromium. [0;32m[ RUN ] [mCertVerifyProcTest.EVVerification [20173:20173:0624/225722:2591674974614:ERROR:cert_verify_proc_nss.cc(853)] CERT_PKIXVerifyCert for comodo.com failed err=-8181 net/cert/cert_verify_proc_unittest.cc:122: Failure Value of: error Actual: -201 Expected: OK Which is: 0 net/cert/cert_verify_proc_unittest.cc:123: Failure Value of: verify_result.cert_status & CERT_STATUS_IS_EV Actual: false Expected: true [0;31m[ FAILED ] [mCertVerifyProcTest.EVVerification (7 ms)