Ricardo Escobar Barrios

I was observing an issue similar to this reported on testfx (https://github.com/microsoft/testfx/issues/2563#issuecomment-2151062114), having random fails with various causes, testing many versions from 1.3.0 to 6.0.2 all failed (1.3.0 had previously...

I believe this (https://github.com/microsoft/testfx/issues/2563) issue on testfx is caused by this one

I'm having this same issue when running test during a Docker container build, it seems to be a race condition during the assemblies instrumentation because when it's run in a...

Thanks for your response, I will create the issue and mention this one on it, but as I said in my comment, I'm also experimenting the exact same issues reported...

This is the full command that I'm using `dotnet test XXXXXX.sln -c Release -o /app/build --collect:"XPlat Code Coverage" --logger:"junit;LogFilePath=../../artifacts/{assembly}-test-result.xml;MethodFormat=Class;FailureBodyFormat=Verbose"` and it's run during a docker build, this works fine if...

My issue seems to be caused by coverlet, I "solved" my case by limiting the cpu count during test using `-maxcpucount:1` switch ([link to docs](https://learn.microsoft.com/en-us/visualstudio/msbuild/building-multiple-projects-in-parallel-with-msbuild?view=vs-2022#-maxcpucount-switch)), my builds seems to now...