-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[Android][infra] Increase the Android test coverage across different OS versions #102555
Comments
Tagging subscribers to 'arch-android': @steveisok, @akoeplinger |
Tagging subscribers to this area: @directhex |
We do have Helix queues for the newer API levels, it just never was worth the CI cost and pain of triaging flaky issues to keep them enabled all the time. We used a temporary PR (#64341) to trigger the "full" set from time to time, but nowadays having a separate pipeline probably makes more sense. |
I think a temporary PR might be a good idea as well. Our initial idea was to do ~weekly runs but as you mentioned it depends on the CI cost and flakiness of the issues. I think it also depends on how many really issues we can discover using this approach and perhaps just a selected set of Libraries test could be run if they are prone to breaking changes by Android OS bumps. |
IMO trying to guess which tests could be broken is kinda impossible, much easier to run everything. If you only run weekly it should be manageable to deal with the flaky issues. |
For .NET 9, we support Android API version of 21 and newer (https://github.com/dotnet/core/blob/main/release-notes/9.0/supported-os.md#android). Our CI infrastructure only test a fixed API version:
runtime/eng/pipelines/libraries/helix-queues-setup.yml
Lines 94 to 98 in 9a18cf5
We should explore the possibility of having coverage over both older and newer Android API version for the Libraries tests.
TODO:
The text was updated successfully, but these errors were encountered: