Instrumenting ASP.NET Core Views.dll takes >20 minutes
See original GitHub issueOn both Azure DevOps and GitHub Actions I am coming across the same issue. Since upgrading to ASP.NET Core 3.1, calling the following code takes over 20 minutes to execute, and will often cause the build to fail due to timeout:
dotnet test --configuration Release /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:Exclude="[ActionsTest.Views.dll]*%2c[xunit.*]*"
The Solution contains one ASP.NET Core 3.1 application, and a number of .Net Standard 2.0 class libraries. By running dotnet test
on each project individually, it is only the ASP.Net Core project that takes so long (all the others take a reasonable length of time to complete, a few seconds to 1-2 minutes for a large one).
By setting the verbose
flag, I can see that the line that takes to long is the second line (I’ve added the previous line to show the timestamp):
Mon, 16 Mar 2020 15:25:11 GMT
[coverlet] Instrumented module: 'D:\a\ActionsTest\ActionsTest\tests\ActionsTest.Test\bin\Debug\netcoreapp3.1\ActionsTest.dll'
Mon, 16 Mar 2020 15:49:44 GMT
[coverlet] Instrumented module: 'D:\a\ActionsTest\ActionsTest\tests\ActionsTest.Test\bin\Debug\netcoreapp3.1\ActionsTest.Views.dll'
It seems that
- the Exclude parameter isn’t excluding the ActionsTest.Views.dll assembly, and
- Instrumenting *.Views.dll takes a huge amount of time
Please let me know if you need any more information.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top GitHub Comments
"
)PS thank you for your work on this project, it’s really appreciated 🙂 PPS I hope the current situation in Italy improves soon! 🙏
Thank’s for patience and for using coverlet
Thank’s we’re fighting, we’ll make it!