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
- src/libraries/System.Security.Cryptography*/
- src/libraries/Common/src/System/Security/Cryptography/
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