Reduce Process test time

[stephentoub]

Fix a test that was taking 30 seconds, and make another test outerloop.

cc: @danmosemsft

[ghost]

Tagging subscribers to this area: @eiriktsarpalis, @jeffhandley
See info in area-owners.md if you want to be subscribed.

---

Issue meta data

Issue content:
	Fix a test that was taking 30 seconds, and make another test outerloop. cc: @danmosemsft </td>
Issue author:		stephentoub
Assignees:	-
Labels:	`area-System.Diagnostics.Process` </td>
Milestone:	-

[danmoseley]

How did I not think of doing it this way?

[ghost]

Hello @danmosemsft!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[danmoseley]

Strictly, it would be possible to implement p.Kill() such that it caused the wait (using method on the same process object) to complete (as tested here) but independently terminating the process (or allowing it to exit) did not. I guess that's what I was thinking.

[stephentoub]

Strictly, it would be possible to implement p.Kill() such that it caused the wait (using method on the same process object) to complete (as tested here) but independently terminating the process (or allowing it to exit) did not. I guess that's what I was thinking.

If that was really a concern, Kill could be called on a Process.GetProcessById(p.Id) object. But I don't think it matters right now.

[danmoseley]

Yes it's not worth more time.

[danmoseley]

@steveisok two of the Android tests failed thus:

[16:20:16] dbug: Executing command: '/home/helixbot/work/9E7008EA/p/microsoft.dotnet.xharness.cli/1.0.0-prerelease.20559.2/runtimes/any/native/adb/linux/adb  start-server'
[16:20:16] dbug: 
[16:20:16] dbug: Executing command: '/home/helixbot/work/9E7008EA/p/microsoft.dotnet.xharness.cli/1.0.0-prerelease.20559.2/runtimes/any/native/adb/linux/adb  devices -l'
[16:20:16] dbug: Unexpected response from adb devices -l:
                 Exit code=0
                 Std. Output: List of devices attached

[danmoseley]

FileSystemWatcher failure is already tracked by #24181