[Mono] Fix android rolling build failures #61343
Comments
dotnet-issue-labeler
bot
added
area-Infrastructure-mono
untriaged
|
Tagging subscribers to this area: @directhex Issue DetailsInside the rolling build for the main pipeline there are a set of tests that consistently fail. The goal should be to determine why they are failing. try to fix (if possible), and get the legs to pass. In this case, there appear to be similarly failing tests in both the
|
|
Tagging subscribers to 'arch-android': @steveisok, @akoeplinger Issue DetailsInside the rolling build for the main pipeline there are a set of tests that consistently fail. The goal should be to determine why they are failing. try to fix (if possible), and get the legs to pass. In this case, there appear to be similarly failing tests in both the
|
ghost
added
in-pr
marek-safar
removed
the
untriaged
There are connectivity issues on some physical Android devices. We should disable the affected tests until the issue isn't resolved. Ref #61343
ghost
added
the
in-pr
ghost
removed
the
in-pr
ghost
locked as resolved and limited conversation to collaborators
Inside the rolling build for the main pipeline there are a set of tests that consistently fail. The goal should be to determine why they are failing. try to fix (if possible), and get the legs to pass.
In this case, there appear to be similarly failing tests in both the
net7.0-Android-Release-arm-Mono_Release-Windows.10.Amd64.Android.Openand thenet7.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Openruns.The text was updated successfully, but these errors were encountered: