-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/7.0-staging] Disable NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds #96053
[release/7.0-staging] Disable NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds #96053
Conversation
…g_Succeeds The 3rd party service has expired certificate
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBackport of #79407 to release/7.0-staging /cc @rzikm Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Test-only change => tell mode, adding Servicing-approved |
CI Failures are unrelated. |
Backport of #79407 to release/7.0-staging
6.0 PR is #96055
Fixes #91705
/cc @rzikm, @karelz
Customer Impact
Test only change to clean up CI. The test uses external server (badssl.com) which has now expired certificate (see also chromium/badssl.com#515). The test fails because the certificate validation errors differ from the tests expectations.
Testing
Will run CI to check affected test.
Risk
Low, test-only change.