-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
System.Security.Cryptography.X509Certificates.Tests.ChainTests.BuildInvalidSignatureTwice failure #65448
Comments
Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
runfo has been attributing these to #25979, but these failures looks different - especially since one of them in on non-Windows. |
The failures that I see in Kusto generally map to known conditions
The exceptions being the one reported in the title here (where chain build 1 failed, which we could improve our diagnostics on), and a couple of PRs (one seems to have broken ReadLink, another was PR #70941 (which seems to have broken runtime/src/libraries/Common/tests/System/Security/Cryptography/ByteUtils.cs Lines 24 to 35 in 0c4ee9e
|
The WASM failure that recently got added here is erroneous. This test was not supposed to run on WASM. |
@jeffhandley a decent amount of failures started popping up again this week against some of the mono configurations. Can you have someone take a look? |
Closing in favor of #82837 as it'll be tagged as a know build error in the Build Analysis tab. |
Runfo Tracking Issue: System.Security.Cryptography.X509Certificates.Tests.ChainTests.BuildInvalidSignatureTwice failure
Build Result Summary
The text was updated successfully, but these errors were encountered: