You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new [Intel based Windows pool][0] has been configured to run Android
emulator test jobs on. This pool currently has capacity to scale up to
10 agents.
The `StartAndroidEmulator` task and the execution environment for the
`AcquireAndroidTarget` target have been updated to address issues with
emulator launch attempts hanging on these Windows VMs with this
seemingly related output:
The STDIO streams did not close within 10 seconds of the exit event from process 'C:\Program Files\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited.
A new "Windows > Tests > Debugging" job has been added to the MSBuild
Device tests stage that currently runs all tests in the `DebuggingTest`
category.
Starting with only one new job will allow us to start to scale up on
Windows while monitoring for potential performance/reliabilty issues.
[0]: https://ms.portal.azure.com/?feature.customportal=false#@microsoft.onmicrosoft.com/resource/subscriptions/cd4829e2-e38b-43d2-8316-2f2009f36f97/resourcegroups/1ESobjects/providers/Microsoft.CloudTest/hostedpools/Android-1ESPT/overview
Copy file name to clipboardExpand all lines: build-tools/Xamarin.Android.Tools.BootstrapTasks/Xamarin.Android.Tools.BootstrapTasks/StartAndroidEmulator.cs
+22-36
Original file line number
Diff line number
Diff line change
@@ -37,13 +37,13 @@ public class StartAndroidEmulator : Task
0 commit comments