You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PublishCodeCoverageResults@2 fails to publish the coverage report when there are more than 1800 files in it. I don't have a hard number, but I have builds with ~500 files in the report that work properly and builds with 1800+ that get 60+% of the way through uploading the files and then just stop without any errors.
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
Windows Server 2019 and 2022
Relevant log output
Publishing coverage summary data.
line- 35973 of 316641 covered.
Publishing file coverage data.
Publishing code coverage HTML report.
Uploading 4750 files.
Total file: 4750 ---- Processed file: 47 (0%).
Total file: 4750 ---- Processed file: 155 (3%).
Total file: 4750 ---- Processed file: 264 (5%).
Total file: 4750 ---- Processed file: 390 (8%).
Total file: 4750 ---- Processed file: 525 (11%).
Total file: 4750 ---- Processed file: 613 (12%).
Total file: 4750 ---- Processed file: 668 (14%).
Total file: 4750 ---- Processed file: 741 (15%).
Total file: 4750 ---- Processed file: 819 (17%).
Total file: 4750 ---- Processed file: 946 (19%).
Total file: 4750 ---- Processed file: 1076 (22%).
Finishing: Publish code coverage results
New issue checklist
Task name
PublishCodeCoverageResults
Task version
2.242.1
Issue Description
PublishCodeCoverageResults@2 fails to publish the coverage report when there are more than 1800 files in it. I don't have a hard number, but I have builds with ~500 files in the report that work properly and builds with 1800+ that get 60+% of the way through uploading the files and then just stop without any errors.
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 Server 2019 and 2022
Relevant log output
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: