Uh oh!
There was an error while loading. Please reload this page.
Disable some suspicious tests which might lead to OOM crashes on Android emulators and arm64 devices - #62767
Conversation
…on Android emulators and arm64 devices
ghost
commented
Dec 14, 2021
Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones, @krwq Issue DetailsJust blindly disabling several crypto test classes near which crashes have been observed for a while (based on a couple of the mobile targets rolling build runs).
|
MaximLipnin
commented
Dec 14, 2021
/azp run runtime-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
steveisok
commented
Dec 14, 2021
/azp run runtime-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
steveisok
commented
Dec 15, 2021
@akoeplinger Ideally, I'd like to run less iterations of tests if we can. Would it be better to skip the crypto suite outright on emulators in order to have max coverage that runs on devices? |
…WriteSubjectPublicKeyInfo()
akoeplinger
commented
Dec 16, 2021
Hm I think it should be possible to reduce the iteration count for the tests, but I haven't looked too deeply. I'm fine with disabling for now. |
MaximLipnin
commented
Dec 17, 2021
/azp run runtime-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
MaximLipnin
commented
Dec 17, 2021
There is sill a crash on |
Yeah if you look a little further in that adb log you can see that essentially the whole system crashed and rebooted. That might be still because of the crypto tests e.g. if they still consume too much RAM and the system gets overloaded, but I think we can monitor that in the rolling build and react if necessary. |
Just blindly disabling several crypto tests near which crashes have been observed for a while (based on a couple of the mobile targets rolling build runs).
Disabled tests:
See also #62547.
cc @steveisok@akoeplinger