Escape hatch: share stdout with node children

Merged
RA
9y ago
+31-12

The VSTest runner emits log messages to its stdout. So far, in .NET
Core, that has resulted in them getting piped all the way up through
the worker MSBuild that launched the task, the entry-point MSBuild
coordinating the build, and the dotnet test invocation that started
it all.

The introduction of node reuse for .NET Core makes this untenable:
worker nodes should not share stdout with the process that happened to
launch them, because they will be long-lived and may do entirely
unrelated builds.

But for now, this breaks the dotnet test scenario. This commit creates
an escape hatch environment variable
MSBUILDENSURESTDOUTFORTASKPROCESSES that can be used in combination
with /nodereuse:false to create a cone of MSBuild processes that all
share std handles.

Enables workaround for Microsoft/vstest#1503.