Use new Microsoft.DotNet.RemoteExecutor package

[Anipik]

Dotnet team just added a new package in the arcade repo called Microsoft.DotNet.RemoteExecutor package. dotnet/arcade#2176

We use a lot of code from this project to run our tests. This code was added in #2200

Although slight modifications were made to the code to handle Microsoft.ML based scenarios.
But i think we should be able to use this package to run other tests.

cc @ViktorHofer

[eerhardt]

Note that dotnet/machinelearning doesn't use dotnet/arcade at all just yet. Will it be possible to use just the RemoteExecutor package without upgrading the rest of the build system to arcade?

[ViktorHofer]

Sure, just consume the dotnet-core feed: https://github.com/dotnet/arcade#getting-started

[mstfbl]

Closing this issue as no further updates on the issue have been given. @Anipik feel free to reopen the issue if you can provide more information. Thanks.

[ViktorHofer]

Curious why the "need-more-info" label was applied even though no question was asked? This issue shouldn't be closed as it still applies.

[harishsk]

Can you please share what the Microsoft.DotNet.RemoteExecutor is and why we should be using it?
We have a plan to upgrade to to Arcade. But it is not high priority right now.

[ViktorHofer]

Can you please share what the Microsoft.DotNet.RemoteExecutor is

Out of process execution of test code. Necessary when environment variables or other process states need to be mutated.

and why we should be using it

You are already using it:

machinelearning/test/Microsoft.ML.TestFramework/RemoteExecutor.cs

Line 21 in 449719c

public static class RemoteExecutor

. This is an outdated copy from CoreFx. Meanwhile we moved RemoteExecutor to Arcade.

The ask is that you get rid of the copy and just use the nuget feed from Arcade. There's no dependency on "arcadifying" the dependency to consume that package. It's just a nuget package which lives on a feed. Let me know if you need more details.

[ViktorHofer]

@mstfbl can we please reopen the issue before it's lost in dev/null?