System.Net.Requests: Pick correct RemoteExecutor overload in test

[akoeplinger]

The test was using RemoteExecutor.Invoke(Action<string, string, string, string> method, ...) since there is no overload that takes Func<string, string, string, string, Task> (only one with three strings) and that means it's becoming an async void.

The delegate that gets invoked will return the moment the method awaits something not yet completed, so now there's a race condition, where RemoteExecutor.Invoke thinks all work is done, but there's still likely work running and it'll start doing all its cleanup stuff like killing child processes.

Fix by removing one string parameter so it picks the correct overload. I'll also open an arcade PR to add an overload with four string arguments.

Fixes #74667

[ghost]

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

Issue Details

---

The test was using RemoteExecutor.Invoke(Action<string, string, string, string> method, ...) since there is no overload that takes Func<string, string, string, string, Task> (only one with three strings) so we weren't awaiting the Task.

Fix by removing one string parameter so it picks the correct overload.

Fixes #74667

Author:	akoeplinger
Assignees:	-
Labels:	area-System.Net
Milestone:	-

[tmds]

The delegate that gets invoked will return the moment the method awaits something not yet completed, so now there's a race condition, where RemoteExecutor.Invoke thinks all work is done, but there's still likely work running and it'll start doing all its cleanup stuff like killing child processes.

For the parent, that means the child is short-lived. It shouldn't cause a situation where the child goes missing (Error while reaping child. errno = 10).

This could be triggering the issue, but it is not the root cause.

[akoeplinger]

@tmds you were right, we're still seeing this on Mono in CI even after this fix so this is actually an unrelated issue. I'll disable the tests again.