You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
System.Net.Requests: Pick correct RemoteExecutor overload in test (#74994)
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
0 commit comments