Azure-pipelines-tasks: Code coverage summary was found, but no artifacts were present to fetch the summary file

Created on 9 Jul 2016  路  20Comments  路  Source: microsoft/azure-pipelines-tasks

snip_20160708232151
image
i converted opencover xml to cobertura format.
I gave the cobertura.xml in the publish code coverage task.I am getting the attached error message.

Please help me resolving the issue

Test bug

Most helpful comment

The issue is with the extension of html files. We support .html files., But the report generator has generated .htm files. We will fix this.

All 20 comments

Can you please past the screenshot of Artifacts?
Is there any folder with name Code Coverage Report under Artifacts?

image

Yes. Please find the attached image

I am using opencover to generate the codecoverage xml(https://github.com/OpenCover/opencover) for asp.net 5 DNX application. After that i am using Reportgenerator to generate the htmls.(https://github.com/danielpalme/ReportGenerator) .VSTS supports Cobertura in the publish task so i converted the opencover coverage xml to Cobertura using https://github.com/danielpalme/OpenCoverToCoberturaConverter.

Please let me know if you need more information.

@nanivijay the folder name should be in this format Code Coverage Report_buildId
how are you publishing these reports?

@nigurr The folder name is as expected.
image

image
image

any pointers????

Does OpenCoverToCoberturaConverter not create HTML files also? I am not sure how similar the format of Cobertura HTML is to that generated by ReportGenerator. Thanks!

OpenCoverToCoberturaConverter is converting the opencover summary xml to Cobertura xml format.
The publish task is not taking care of creating htmls if we provide xml? reportgenerator generates based on xml.

@nanivijay we don't generate HTML based on XML file currently.

@nanivijay
Thanks for the information. Like Nitin said, we do not create HTML files. We are investigating why your uploaded HTML files are not working and I will get back to you next week on that. As a workaround, you can download your HTML artifacts and open them locally in a browser.

@nigurr @atinb Thank you guys.

The issue is with the extension of html files. We support .html files., But the report generator has generated .htm files. We will fix this.

@AshwiniChalla renaming htm to html worked for me. i can use this work around until you fix. Thanks

Great! Thanks for confirming

any plans to support opencover format in vsts code coverage publish tasks?

No current plans. Thanks!

Exploring still the .htm vs .html issue. When are you expecting to fix that? :)

The fix should be deployed within a week. Thanks!

hi experts,

i use coverage.py to run the tests, and to generate the report coverage.xml

but vsts is asking for summary file, and keeps complainting about
"2016-08-01T19:53:05.6705490Z Reading code coverage summary from '/home/_work/4/s/coverage.xml'
2016-08-01T19:53:05.6754020Z ##[warning]No coverage data found. Check the build errors/warnings for more details.

if i use "coverage report", i can see the coverage stat.

any help here?

thanks

I commented on #2186 that you opened. lets use that to track the issue.
Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jared-hexagon picture jared-hexagon  路  3Comments

timfish picture timfish  路  3Comments

MichaelWhiteCodingForFun picture MichaelWhiteCodingForFun  路  3Comments

montebhoover picture montebhoover  路  3Comments

TheRealEdwardCullen picture TheRealEdwardCullen  路  3Comments