Skip to content
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

Publish Code Coverage failing with ##[error]NoInputFiles #19270

Open
1 of 4 tasks
gavintoddchurch opened this issue Nov 13, 2023 · 5 comments
Open
1 of 4 tasks

Publish Code Coverage failing with ##[error]NoInputFiles #19270

gavintoddchurch opened this issue Nov 13, 2023 · 5 comments

Comments

@gavintoddchurch
Copy link

gavintoddchurch commented Nov 13, 2023

Task name

PublishCodeCoverageResults

Task version

2.x

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Ubuntu 22.04

Question

We just moved from the V1 to the V2 and on projects that dont have any coverage were getting ##[warning]No code coverage results were found to publish.
but no when we moved to V2 if that same teams runs they are getting
##[warning]No code coverage results were found to publish.
##[warning]Cant find loc string for key: NoInputFiles
##[error]NoInputFiles

coming from this function call
https://github.com/microsoft/azure-pipelines-tasks/blob/8b5f195ca075a581e57e9f1df6a8c12bc83a3cf4/Tasks/PublishCodeCoverageResultsV2/publishcodecoverageresults.ts#L27

This is the line throwing the error 
https://github.com/microsoft/azure-pipelines-tasks/blob/8b5f195ca075a581e57e9f1df6a8c12bc83a3cf4/Tasks/Common/coveragepublisher/coveragepublisher.ts#L19

We have the failIfCoverageEmpty set to false so we weren't expecting this behavior. Is this something expected?
@gavintoddchurch
Copy link
Author

We have a work around for teams but is this expected behavior?

@henri-kohlberg
Copy link

We have the same issue in our pipelines.

@GavinToddlds Did you just switch back to V1 or do you have another workaround?

@gavintoddchurch
Copy link
Author

No our workaround isn't great. It is just adding a parameter in our template that we validate against before running the task instead of letting it run and not publish anything.

I am still hoping to get some information back if this is expected behavior on the V2 or not.

@j-d-harvey
Copy link

@vinayakmsft is this something you can help with?

@gavintoddchurch
Copy link
Author

Is there someone who can take a look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants