Android queues capacity investigation

[missymessa]

See discussion here: https://teams.microsoft.com/l/message/19:afba3d1545dd45d7b79f34c1821f6055@thread.skype/1750267994268?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=4d73664c-9f2f-450d-82a5-c2f02756606d&parentMessageId=1750267994268&teamName=.NET%20Core%20Eng%20Services%20Partners&channelName=First%20Responders&createdTime=1750267994268

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

[kotlarmilos]

We’re hitting a bottleneck with both Android devices and emulators if we enable dotnet runtime tests on CoreCLR: dotnet/runtime#116540 (comment)

Android emulator queues are using linux machines without actual devices. There should be enough devices to run the runtime and library tests on rolling builds and extra-platform pipeline. Android devices are probably limited.

We need to estimate throughput for Android devices and emulators. Currently, we run a subset of library tests on dotnet/runtime pipeline (each PR) and the full set of library tests on the rolling builds and extra-platforms. I suggest to list number of devices in these queues and the average number of jobs/waiting times.