Andrey Akinshin

@timcassell thanks for the report! Indeed, this issue occurs from time to time (but not every time!) When I set up the test reports, I tried to handle this problem,...

Hey @workgroupengineering, sorry for such a delay. #1796 looks pretty good to me. I have left a few minor comments there. Once you resolve them, I will merge the PR.

@adamsitnik so, do I understand correctly that we are going to replace ```cs { LogKind.Help, ConsoleColor.DarkGreen }, ``` with ```cs { LogKind.Help, ConsoleColor.White }, ``` ?

It seems that creating a palette based on the 16 terminal colors that look nice in all possible color themes in all possible terminals is an unsolvable task. Each terminal...

@adamsitnik could you please take a look?

@caaavik-msft thanks for the update, much appreciate it. I guess, we can support it not on the vstest side, but on the IDE side. At least, I can try to...

@Windows10CE thanks for the bug report! Indeed, the Mono support on Linux has been broken since v0.13.3. If we remove the "The Roslyn toolchain is only supported on .NET Framework"...

While `ConsoleColor.Green` may look better than `ConsoleColor.DarkGreen` in some dark-themed terminals, it may also look less readable in some light-themed terminals. That's how the suggested change looks in the default...

@Taneeda thanks for the detailed report! It is a side effect of anonymous pipes that were introduced in v0.13.3: now native BenchmarkDotNet logs are handled asynchronously from handling the direct...

@Taneeda > from `GlobalCleanup()` which I read from log file in later process The fact that the BenchmarkDotNet log contains the output of your benchmarks is a side-effect of the...