-
Notifications
You must be signed in to change notification settings - Fork 5k
Consider running System.Security.Cryptography tests on Windows 10 Threshold #115162
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
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
/cc @dotnet/area-system-security |
Here are the set of different libraries test runs for windows - runtime/eng/pipelines/libraries/helix-queues-setup.yml Lines 103 to 125 in 43955cb
Do you see something here that would cover this? Maybe outerloop or extra-platforms? |
This issue has been marked |
It appears that the JIT will run some of its tests in a pipeline with Windows 10 / Windows Server 2016 SP0 (Threshold). However, this pipeline will not be triggered for Libraries-only changes.
System.Security.Cryptography is a little sensitive to OS versions, particularly around PKCS12/PFX. There are known differences between Windows 8, Threshold, and Redstone 2+. This has led to a few cases where a test was green and merged because it ran on "new" Windows, only to later find out that the test fails on Windows 10 Threshold when a JIT pipeline runs.
Examples:
Ideally, Windows 10 SP0 / Threshold would be used for library runs that touch cryptography, or a reasonable as possible. A set of path filters might look like
The text was updated successfully, but these errors were encountered: