Messages from xunit tests are randomly mixed with message from the msbuild console logger in stdOut

[NikolayPianikov]

Steps to reproduce

dotnet create xunit
dotnet test --verbosity diagnostic

You can find messy messages by text Test Execution Command Line Tool Version

Expected behavior

Each message should be on the own line and should not be mixed

Actual behavior

Messages are mixed, sometimes happens that one message is interrupted by another in the middle.

See the attached

Environment data

dotnet --info
.NET Command Line Tools (2.1.201)

Product Information:
Version: 2.1.201
Commit SHA-1 hash: 7932dc6

Runtime Environment:
OS Name: Windows
OS Version: 10.0.17134
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.201\

Microsoft .NET Core Shared Framework Host

Version : 2.0.7
Build : 2d61d0b043915bc948ebf98836fefe9ba942be11

[NikolayPianikov]

It could be fixed by the additional argument /m:1, but would not like to do it

[livarcocc]

cc @rainersigwald

Is there anything to coordinate the output from different msbuild nodes?

[rainersigwald]

This is another symptom of microsoft/vstest#1503. Because VSTest doesn't participate in MSBuild's logging infrastructure, it doesn't get our protections on not interleaving messages.

I don't think there's anything we can do within the current infrastructure to fix this; we need to change VSTest to use logging, and that requires a better colorization-of-logging story.

cc @smadala

[livarcocc]

Going to close this one since we already have an issue in VSTest tracking it.