Test failure: System.Security.Cryptography.X509Certificates.Tests.RevocationTests.TimeoutTests.RevocationCheckingDelayed(pkiOptions: OcspEverywhere)

[v-haren]

failed in job: runtime-libraries-coreclr outerloop 20200920.1

net5.0-Windows_NT-Release-x86-CoreCLR_release-Windows.7.Amd64.Open

Error message

watch.Elapsed: 00:00:00.0048075
Expected: True
Actual:   False


Stack trace
   at System.Security.Cryptography.X509Certificates.Tests.RevocationTests.TimeoutTests.RevocationCheckingDelayed(PkiOptions pkiOptions) in /_/src/libraries/System.Security.Cryptography.X509Certificates/tests/RevocationTests/TimeoutTests.cs:line 67

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @jeffhandley
See info in area-owners.md if you want to be subscribed.

[vcsjones]

Ah, okay. I see how this is possible. The retry kicked in. Even though the first attempt failed (maybe because the build servers are so busy right now), Windows was eventually able to get the OCSP response in cache. When we retry, we don't retry with a new certificate, so it builds much faster than expected.

I will see how to best address this.