Warnings are not written out

[nohwnd]

Describe the bug

When class fails to discover there is no warning.

Steps To Reproduce

The project below is broken, when you will run it using vstest console from nuget package it fails to load system.valuetuple, because of the binding redirect in app.config.

This will prevent classes to be discovered, but all the details are swallowed and reported neither to screen, nor to tptrace.

Looks like eqTrace might not be getting the real settings because we in appdomain (this is netframework project).

And the warnings I did not investigate yet.

S:\t\mstest229> dotnet build
S:\t\mstest229> $env:vstest_host_debug_attachvs=0; C:\Users\jajares\.nuget\packages\microsoft.testplatform\17.13.0\tools\net462\Common7\IDE\Extensions\TestPlatform\vstest.console.exe bin\Debug\net472\mstest229.dll  /Diag:logs/vstest.console.diagnostics.TpTrace.log /inisolation

mstest229.zip

Note that we would be glad if you could enclose a repro (zip or link to some GitHub project).
-->

Expected behavior

I am told what was the cause of the issue, and that some classes were not discovered.

Actual behavior

Additional context

[nohwnd]

This is where we get the messages logged including the details of the assembly load failure, but the messages don't end up anywhere. eqtrace is set to false.

make sure you run /inisolation to use attach vs (or use the one that attaches to runner)

warnings also look like they don't propagate back from the appdomain, where we pass an instance of list, not 100% sure, I thought the marshalling is clever enough to handle that.