-
Notifications
You must be signed in to change notification settings - Fork 540
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
[ci] Add Windows 'DebuggingTest' job #9951
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
p.OutputDataReceived += WriteProcessOutputMessage; | ||
p.ErrorDataReceived += WriteProcessErrorMessage; | ||
|
||
p.BeginOutputReadLine (); | ||
p.BeginErrorReadLine (); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, was it specifically these lines that made Run()
never return on Windows?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this seemed to fix things in CI, though I never had this issue when running locally on Windows strangely enough
A new Intel based Windows pool 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 theAcquireAndroidTarget
target have been updated to address issues withemulator launch attempts hanging on these Windows VMs with this
seemingly related output:
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.