-
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
Run just Android Arm64 System.Security.Cryptography.Pkcs.Tests #56861
Run just Android Arm64 System.Security.Cryptography.Pkcs.Tests #56861
Conversation
Tagging subscribers to this area: @directhex Issue DetailsEvaluating #37094
|
1dd2077
to
2112f85
Compare
These still fail on the Android x64/x86 jobs in runtime-staging: https://dev.azure.com/dnceng/public/_build/results?buildId=1277052&view=logs&jobId=df0d4348-1948-576c-9bcf-0f0eaa3c5cab&j=b6e5d97f-d4f8-506b-9e47-e3e32385754a&t=94ce2805-f3e2-5f9a-1d92-0da5613f733d |
Ah, yeah, these ones make the emulator run low on memory for some reason. We could never reproduce locally. |
System.Security.Cryptography.Pkcs.Tests no longer fails on CI from running out of memory after the change, the only failure in runtime-staging for Android is due to System.Runtime.InteropServices, which is addressed by #56909 |
Fixes #37094
This PR reenables System.Security.Cryptography.Pkcs.Tests on Android for x64,x86, arm64.
The tests run out of memory, especially when hitting
DecodeWithHighPbeIterations
as discovered by @akoeplinger , so we have opted to reduce the iteration count forDecodeWithHighPbeIterationsData
for Android in order to still run the tests.