-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrating to 2.0.0 #107
Comments
I'm seeing this also when I run on our jenkins-ci |
Same results in this environment from command-line (1.2.0 works; 2.0.0 reports zero hits) Linux 904f5451827d 4.9.87-linuxkit-aufs #1 SMP Wed Mar 14 15:12:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Product Information: Runtime Environment: Microsoft .NET Core Shared Framework Host Version : 2.0.5 Command-line: using a different output format has no effect |
@razzeee, @xtiancapil, @dlkay0 see my comments in #110, it looks like it's an issue with Linux and/or 2.0.5 |
Hi @razzeee @xtiancapil @dlkay0 did #110 fix this? |
#110 is an issue and thus doesn't fix stuff ;) So you're saying I should try #110 (comment) excluding the test adapter? |
@razzeee yes that's what I meant. Sorry for not being more specific |
So I did run Our docker image is based on microsoft/dotnet:2.0.5-sdk-2.1.4 I can update it, but it's quiet some work |
For Windows Build Agent: Downgrading coverlet.msbuild package to 1.2.0 worked on VSTS Windows Build Agent. Getting the code coverage report. Sonar publish working as well. Test Adapter is MSTest, haven't tested with others yet. |
Thanks for the update @melih154, I'm still unable to reproduce this in Linux |
I had the same issue with core 2.1. I downgraded coverlet to 1.2 and all returns to normal. Setup is jenkins-ci using aws codebuild and a custom linux image from the official docker dotnet-sdk. Docker file is just "FROM microsoft/dotnet:2.1-sdk" Build command dotnet test MyTestProject.csproj /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutputDirectory=../Tests --logger:trx -r ../Tests I have 0% coverage, but only for the "Web" project with Mvc etc in it. I have two other projects in the solution which have coverage coming from them correctly. That's all from the same build and test command Hope that helps. |
@aburgett87 I've also managed to get colored source to display. My issue is resolved. |
It's working for us again. Using the latest version in combination with dotnet core 2.1 |
Hey there,
just a quick heads up. When I update our sources to 2.0.0, it still runs the tests and works fine locally. But if I run it on our gitlab-ci the tests run and coverage gets reported as zero percent on the commandline.
The text was updated successfully, but these errors were encountered: