You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proc dump location: D:\workspace\_work\1\s\.tools\ProcDump\procdump.exe
Running 2 test assemblies in 2 partitions
1 running, 1 queued, 0 completed
Roslyn Error: test timeout exceeded, dumping remaining processes
Dumping dotnet 5796 to D:\workspace\_work\1\s\artifacts\log\Debug\dotnet-1.dmp ... succeeded (100469002 bytes)
Dumping dotnet 5744 to D:\workspace\_work\1\s\artifacts\log\Debug\dotnet-2.dmp ... succeeded (105067654 bytes)
Dumping testhost.net472.x86 2520 to D:\workspace\_work\1\s\artifacts\log\Debug\testhost.net472.x86-3.dmp ... succeeded (325525651 bytes)
Copying ServiceHub logs to D:\workspace\_work\1\s\artifacts\log\Debug
##[error](NETCORE_ENGINEERING_TELEMETRY=Test) Tests failed
This is cryptic and hard to diagnose. Can we instead print out the test log failure info? It looks like we have it somewhere, so it would just be about printing it to the console.
The text was updated successfully, but these errors were encountered:
This type of failure is diagnosed by downloading the heap dump and finding the deadlock. Historically, test logs have not made the investigation any easier so the emphasis is on ensuring the heap dump is available.
I have run into this many times before and it's an utter PITA. Please provide just the test that was running. We can still keep providing the heap dumps if hte dev needs that.
Right now all you see are things like:
This is cryptic and hard to diagnose. Can we instead print out the test log failure info? It looks like we have it somewhere, so it would just be about printing it to the console.
The text was updated successfully, but these errors were encountered: