New issue
Advanced search Search tips

Issue 590868 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Re-enable CertVerifyProcTest.CybertrustGTERoot

Project Member Reported by nek...@chromium.org, Feb 29 2016

Issue description

I had to disable CertVerifyProcTest.CybertrustGTERoot because it was failing on multiple Mac bots. I don't know what patch has caused the test to fail, but from the blame set I found out that you made a change in net/ that might be related:
"net: merge two versions of SetTCPNoDelay() function into one (issue"
Could you re-enable the test once you figure out what is causing the issue? Feel free to re-assign if my quick investigation is wrong.
https://build.chromium.org/p/chromium.memory/builders/Mac%20ASan%2064%20Tests%20%281%29/builds/12559/steps/net_unittests%20on%20Mac-10.9/logs/CertVerifyProcTest.CybertrustGTERoot

 
Pasting error messages from url above:
CertVerifyProcTest.CybertrustGTERoot (run #1):
[ RUN      ] CertVerifyProcTest.CybertrustGTERoot
../../net/cert/cert_verify_proc_unittest.cc:1220: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1221: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1243: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1244: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1266: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1267: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1286: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1287: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
[  FAILED  ] CertVerifyProcTest.CybertrustGTERoot (189 ms)

CertVerifyProcTest.CybertrustGTERoot (run #2):
[ RUN      ] CertVerifyProcTest.CybertrustGTERoot
../../net/cert/cert_verify_proc_unittest.cc:1220: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1221: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1243: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1244: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1266: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1267: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1286: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1287: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
[  FAILED  ] CertVerifyProcTest.CybertrustGTERoot (207 ms)

CertVerifyProcTest.CybertrustGTERoot (run #3):
[ RUN      ] CertVerifyProcTest.CybertrustGTERoot
../../net/cert/cert_verify_proc_unittest.cc:1220: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1221: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1243: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1244: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1266: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1267: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1286: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1287: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
[  FAILED  ] CertVerifyProcTest.CybertrustGTERoot (196 ms)

CertVerifyProcTest.CybertrustGTERoot (run #4):
[ RUN      ] CertVerifyProcTest.CybertrustGTERoot
../../net/cert/cert_verify_proc_unittest.cc:1220: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1221: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1243: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1244: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1266: Failure
Value of: error
  Actual: -202
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1267: Failure
Value of: verify_result.cert_status
  Actual: 524294
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
../../net/cert/cert_verify_proc_unittest.cc:1286: Failure
Value of: error
  Actual: -201
Expected: OK
Which is: 0
../../net/cert/cert_verify_proc_unittest.cc:1287: Failure
Value of: verify_result.cert_status
  Actual: 524290
Expected: CERT_STATUS_SHA1_SIGNATURE_PRESENT
Which is: 524288
[  FAILED  ] CertVerifyProcTest.CybertrustGTERoot (199 ms)
Cc: rsleevi@chromium.org
Components: Internals>Network>SSL
Looks like the certificate in question expired today:

   2016-02-29

So this is not related to the suspected revert in https://codereview.chromium.org/1744153003/.

Ryan, should this test be removed now?
Cc: -rsleevi@chromium.org eroman@chromium.org
Owner: rsleevi@chromium.org
Status: Started (was: Untriaged)
Yes, it should be removed.

https://codereview.chromium.org/1751733002/
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 1 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9ad3f48a16790967f9fc311d83198cc04404b567

commit 9ad3f48a16790967f9fc311d83198cc04404b567
Author: rsleevi <rsleevi@chromium.org>
Date: Tue Mar 01 17:16:59 2016

Remove CertVerifyProcTest.CybertrustGTERoot unit test

This test originally tested a CA-specific workaround in chain building.
However, due to more OS X "quirks", the CA-specific workaround was
replaced with a CA-agnostic one. While this unit test did provide some
value for the specific CA test, it was only relevant on pre-10.9 systems
anyways; with OS X <10.9 being deprecated, this test is no longer
relevant for those platforms.

Given that the CertVerifyProcWeakDigestTest covers the superset of the
GTE issue, simply removing this test is sufficient.

BUG= 590868 
R=eroman@chromium.org

Review URL: https://codereview.chromium.org/1751733002

Cr-Commit-Position: refs/heads/master@{#378462}

[modify] https://crrev.com/9ad3f48a16790967f9fc311d83198cc04404b567/net/cert/cert_verify_proc_unittest.cc
[modify] https://crrev.com/9ad3f48a16790967f9fc311d83198cc04404b567/net/data/ssl/certificates/README
[delete] https://crrev.com/8be1ff11dc1fae61146dbcfaa38e12314d290dca/net/data/ssl/certificates/cybertrust_baltimore_cross_certified_1.pem
[delete] https://crrev.com/8be1ff11dc1fae61146dbcfaa38e12314d290dca/net/data/ssl/certificates/cybertrust_baltimore_cross_certified_2.pem
[delete] https://crrev.com/8be1ff11dc1fae61146dbcfaa38e12314d290dca/net/data/ssl/certificates/cybertrust_baltimore_root.pem
[delete] https://crrev.com/8be1ff11dc1fae61146dbcfaa38e12314d290dca/net/data/ssl/certificates/cybertrust_gte_root.pem
[delete] https://crrev.com/8be1ff11dc1fae61146dbcfaa38e12314d290dca/net/data/ssl/certificates/cybertrust_omniroot_chain.pem

Labels: Merge-Request-49 Merge-Request-50 M-51
49/50 TPMs - disabling & deleting a test to keep your release waterfalls green? :)
Has this been checked into and validated in ToT?
re comment 7: Yes, this is shown by comment #5. As explained, it's disabling & deleting a test that will already fail 100% of the time.

Comment 9 by tin...@google.com, Mar 1 2016

Labels: OS-Mac
Project Member

Comment 10 by bugdroid1@chromium.org, Mar 2 2016

Labels: Merge-Merged-master1
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/bling/chromium.git/+/9ad3f48a16790967f9fc311d83198cc04404b567

commit 9ad3f48a16790967f9fc311d83198cc04404b567
Author: rsleevi <rsleevi@chromium.org>
Date: Tue Mar 01 17:16:59 2016

Comment 11 by tin...@google.com, Mar 3 2016

Labels: -Merge-Request-49 Merge-Review-49 Hotlist-Merge-Review
[Automated comment] There appears to be on-going work (i.e. bugroid changes), needs manual review.

Comment 12 by tin...@google.com, Mar 3 2016

Labels: -Merge-Request-50 Merge-Review-50
[Automated comment] There appears to be on-going work (i.e. bugroid changes), needs manual review.
Labels: -Merge-Review-49 Merge-Approved-49
Merge approved for M49 (branch 2623)


Please merge your change to M49 branch 2623 asap if you think it is a safe merge. We're planning M49 stable candidate cut for next week release on tomorrow, Friday @ 5:00 PM PST.
Project Member

Comment 15 by bugdroid1@chromium.org, Mar 3 2016

Labels: -merge-approved-49 merge-merged-2623
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0d5ba976a8f0e95a76c4b603a75d85c6a84bc0ee

commit 0d5ba976a8f0e95a76c4b603a75d85c6a84bc0ee
Author: Ryan Sleevi <rsleevi@chromium.org>
Date: Thu Mar 03 21:36:56 2016

Remove CertVerifyProcTest.CybertrustGTERoot unit test

This test originally tested a CA-specific workaround in chain building.
However, due to more OS X "quirks", the CA-specific workaround was
replaced with a CA-agnostic one. While this unit test did provide some
value for the specific CA test, it was only relevant on pre-10.9 systems
anyways; with OS X <10.9 being deprecated, this test is no longer
relevant for those platforms.

Given that the CertVerifyProcWeakDigestTest covers the superset of the
GTE issue, simply removing this test is sufficient.

BUG= 590868 
TBR=eroman@chromium.org

Review URL: https://codereview.chromium.org/1751733002

Cr-Commit-Position: refs/heads/master@{#378462}
(cherry picked from commit 9ad3f48a16790967f9fc311d83198cc04404b567)

Review URL: https://codereview.chromium.org/1763853002 .

Cr-Commit-Position: refs/branch-heads/2623@{#571}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}

[modify] https://crrev.com/0d5ba976a8f0e95a76c4b603a75d85c6a84bc0ee/net/cert/cert_verify_proc_unittest.cc
[modify] https://crrev.com/0d5ba976a8f0e95a76c4b603a75d85c6a84bc0ee/net/data/ssl/certificates/README
[delete] https://crrev.com/3f9af68e9892ec825152065246424a23be9ed115/net/data/ssl/certificates/cybertrust_baltimore_cross_certified_1.pem
[delete] https://crrev.com/3f9af68e9892ec825152065246424a23be9ed115/net/data/ssl/certificates/cybertrust_baltimore_cross_certified_2.pem
[delete] https://crrev.com/3f9af68e9892ec825152065246424a23be9ed115/net/data/ssl/certificates/cybertrust_baltimore_root.pem
[delete] https://crrev.com/3f9af68e9892ec825152065246424a23be9ed115/net/data/ssl/certificates/cybertrust_gte_root.pem
[delete] https://crrev.com/3f9af68e9892ec825152065246424a23be9ed115/net/data/ssl/certificates/cybertrust_omniroot_chain.pem

Project Member

Comment 16 by bugdroid1@chromium.org, Mar 4 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/bling/chromium.git/+/0d5ba976a8f0e95a76c4b603a75d85c6a84bc0ee

commit 0d5ba976a8f0e95a76c4b603a75d85c6a84bc0ee
Author: Ryan Sleevi <rsleevi@chromium.org>
Date: Thu Mar 03 21:36:56 2016

Comment 17 by tin...@google.com, Mar 4 2016

Labels: -Merge-Review-50 Merge-Approved-50
Merge approved for M50 (branch 2661). Pls go ahead merge.
Ryan is out of office.

I will handle the merge to M50 (assuming it hasn't already been done).
Project Member

Comment 19 by bugdroid1@chromium.org, Mar 4 2016

Labels: -merge-approved-50 merge-merged-2661
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/589c2ab3c663c6eefed35e132db7c77bfea44c94

commit 589c2ab3c663c6eefed35e132db7c77bfea44c94
Author: Eric Roman <eroman@chromium.org>
Date: Fri Mar 04 22:27:56 2016

Remove CertVerifyProcTest.CybertrustGTERoot unit test

This test originally tested a CA-specific workaround in chain building.
However, due to more OS X "quirks", the CA-specific workaround was
replaced with a CA-agnostic one. While this unit test did provide some
value for the specific CA test, it was only relevant on pre-10.9 systems
anyways; with OS X <10.9 being deprecated, this test is no longer
relevant for those platforms.

Given that the CertVerifyProcWeakDigestTest covers the superset of the
GTE issue, simply removing this test is sufficient.

BUG= 590868 
R=eroman@chromium.org

Review URL: https://codereview.chromium.org/1751733002

Cr-Commit-Position: refs/heads/master@{#378462}
(cherry picked from commit 9ad3f48a16790967f9fc311d83198cc04404b567)

Review URL: https://codereview.chromium.org/1764363002 .

Cr-Commit-Position: refs/branch-heads/2661@{#87}
Cr-Branched-From: ef6f6ae5e4c96622286b563658d5cd62a6cf1197-refs/heads/master@{#378081}

[modify] https://crrev.com/589c2ab3c663c6eefed35e132db7c77bfea44c94/net/cert/cert_verify_proc_unittest.cc
[modify] https://crrev.com/589c2ab3c663c6eefed35e132db7c77bfea44c94/net/data/ssl/certificates/README
[delete] https://crrev.com/389f47fd4af8ff44f8396e353a14b078e500f6f0/net/data/ssl/certificates/cybertrust_baltimore_cross_certified_1.pem
[delete] https://crrev.com/389f47fd4af8ff44f8396e353a14b078e500f6f0/net/data/ssl/certificates/cybertrust_baltimore_cross_certified_2.pem
[delete] https://crrev.com/389f47fd4af8ff44f8396e353a14b078e500f6f0/net/data/ssl/certificates/cybertrust_baltimore_root.pem
[delete] https://crrev.com/389f47fd4af8ff44f8396e353a14b078e500f6f0/net/data/ssl/certificates/cybertrust_gte_root.pem
[delete] https://crrev.com/389f47fd4af8ff44f8396e353a14b078e500f6f0/net/data/ssl/certificates/cybertrust_omniroot_chain.pem

Status: Fixed (was: Started)
Project Member

Comment 21 by bugdroid1@chromium.org, Oct 17 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9204c52f2df95f47190949f7d5fe60e6c1ede337

commit 9204c52f2df95f47190949f7d5fe60e6c1ede337
Author: Eric Roman <eroman@chromium.org>
Date: Tue Oct 17 03:05:47 2017

Remove unused code TestRootCerts::SetAllowSystemTrust().

The method was needed for test CertVerifyProcTest.CybertrustGTERoot (Mac), however it has since been deleted (9ad3f48a16790967f9fc311d83198cc04404b567).

Bug:  590868 
Change-Id: Ie85b19d5665cc6398c34048fc672fce1a9f2a2cd
Reviewed-on: https://chromium-review.googlesource.com/720255
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#509253}
[modify] https://crrev.com/9204c52f2df95f47190949f7d5fe60e6c1ede337/net/cert/test_root_certs.h
[modify] https://crrev.com/9204c52f2df95f47190949f7d5fe60e6c1ede337/net/cert/test_root_certs_mac.cc

Components: Tests>Disabled
Labels: Test-Disabled

Sign in to add a comment