Don't throw from RemoteExecutor on SkipTestExceptions

[MihaZupan]

Fixes #63008

Should be reviewed without looking at whitespace changes.

[ghost]

Tagging subscribers to this area: @dotnet/ncl, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Fixes #63008

Should be reviewed without looking at whitespace changes.

Author:	MihaZupan
Assignees:	-
Labels:	area-System.Net.Security
Milestone:	7.0.0

[wfurt]

LGTM.

[jkoritzinsky]

Is there any interest in generalized support for communicating a SkipTestException from a RemoteExecutor callback back to the test process? Or is this enough of a one-off scenario that it's not worth the effort?

[wfurt]

Is there any interest in generalized support for communicating a SkipTestException from a RemoteExecutor callback back to

I'm not sure @jkoritzinsky. That would be handy in cases when the skip is determined inside of the code that runs inside of the remote. It seems like in most cases we can determine this upfront. In this case, this is caused by this test calling another test that now has SkipTest and this dependency was not obvious.

[jkoritzinsky]

@wfurt In that case, I think this is an obtuse-enough scenario that we don't need to add support to RemoteExecutor directly.