Add RemoteInvokeOptions to EtwManifestGeneration test

[josalem]

No description provided.

[ghost]

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

Issue Details

---

null

Author:	josalem
Assignees:	josalem
Labels:	area-System.Diagnostics.Tracing, test enhancement
Milestone:	6.0.0

[ghost]

Hello @josalem!

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]

Another option we've used in some tests, and we could build into RemoteExecutor, is to have the test continue past the timeout before it fails, so it can tell us how long it ultimately took (or whether it effectively hung).

Eg timeout of 1 minute. Test takes 1:30. Test fails because it took over 1 minute, but logs 1:30 in the failure so we know it was merely slow. We might chose to raise the timeout rather than investigate.

[danmoseley]

Actually it would probably make sense to modify RemoteExecutor do so this automatically, waiting up to eg 2x the specified timeout or 10 minutes whichever is less. That would give us good info from time to time including in this case.