-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG]: PublishCodeCoverageResults@2 Error during reading file #19901
Comments
I've compared the two files generated by the .NET 8 runtime and .NET 7 Runtime. For some reason the filename in the .NET 8 generated one is a url to devops not an actual file path. .NET 7
.NET 8
|
The link being output appears to be a result of using the
|
It looks like setting |
I was able to to resolve this by just using the opencover format which is supported by PublishCodeCoverageResults@2 but not documented. The documentation page for this task https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v2?view=azure-pipelines does not appear to list what formats are supported. |
New issue checklist
Task name
PublishCodeCoverageResults@2
Task version
2.238.1
Issue Description
I recently installed the .NET 8 SDK on my build server and now this task no longer works. Please note my projects still Target .NET 7 and compile without issue. The DotNetCoreCLI@2 tests execution runs without issue as well.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 11
Relevant log output
2024-05-22T18:12:49: Error during reading file 'https://dev.azure.com/MyOrg/MyProject/_apis/git/repositories/my-repo/items?api-version=1.0&versionType=commit&version=sha1&path=/src/MyProject/MyFile.cs': Response status code does not indicate success: 500 (Internal Server Error).
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: