-
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
[mobile] Overview of mobile related CI failures #103472
Comments
Tagging subscribers to 'os-ios': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger |
Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger |
Tagging subscribers to 'os-tvos': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger |
Tagging subscribers to 'os-maccatalyst': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger |
@matouskozak #103406 needs a tweak to not run these tests as BinaryFormatter is no longer supported |
You're right, @adamsitnik is working on that in #103471. |
Description
This issue provides an overview of dotnet/runtime CI (main branch) failures related to .NET mobile platforms. This tracking issue is updated manually. Feel free to update the issue if you encounter any out-of-date information.
Platforms
The failures are divided per mobile platform when possible or categorized as "Other Failures".
Apple
iOS.Simulator.LambdaCompilerAot
tests, attempting to JIT compile method in AOT-only mode, not clear causeSystem.Formats.Tar
testsSystem.IO.UnmanagedMemoryStream.Tests
System.Memory.Tests
Android
Other Failures
Note that the "Impact" column represents impact of the issue to the CI health/state and doesn't necessary correlate with final impact to customer apps.
The text was updated successfully, but these errors were encountered: