[iOS] Use different tvOS helix queue for PR's #72467
Conversation
Up until now, we have used a single tvOS queue for all pipelines. This has lead to frequent timeouts because there simply aren't enough devices to handle spikes in traffic. We will now make use of two queues, one for runtime (PR's) and one for runtime-extra-platforms (scheduled jobs, manual runs). Since we are only running System.Runtime tests on PR's, we should see PR timeouts much less.
ghost
assigned 
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsUp until now, we have used a single tvOS queue for all pipelines. This has lead to frequent timeouts because there simply aren't enough devices to handle spikes in traffic. We will now make use of two queues, one for runtime (PR's) and one for runtime-extra-platforms (scheduled jobs, manual runs). Since we are only running System.Runtime tests on PR's, we should see PR timeouts much less.
|
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
steveisok
force-pushed
the
use-alt-tvos-queues
branch
from
eb31445
to
6f07b2a
Compare
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
steveisok
force-pushed
the
use-alt-tvos-queues
branch
from
6f07b2a
to
467f4d4
Compare
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Up until now, we have used a single tvOS queue for all pipelines. This has lead to frequent timeouts because there simply aren't enough devices to handle spikes in traffic. We will now make use of two queues, one for runtime (PR's) and one for runtime-extra-platforms (scheduled jobs, manual runs). Since we are only running System.Runtime tests on PR's, we should see PR timeouts much less.