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
{{ message }}
This repository has been archived by the owner on Nov 15, 2021. It is now read-only.
When merging multiple results using mergeoutput, if coverbytest is also specified, then the output TrackedMethod elements from each run start with a uid of 1. This causes the uid in the TrackedMethodRef elements to be ambiguous.
This also causes ReportGenerator to crash when reading the resulting report file.
My Framework
.NET 2
.NET 3.5
.NET 4
.NET 4.5
.NET 4.6
.NET 4.6.1
.NET 4.6.2
.NET Core 1.0.0
Something else
My Environment
Windows 7 or below (not truly supported due to EOL)
Windows 8
Windows 8.1
Windows 10
Windows 10 IoT Core
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
I have already...
repeated the problem using the latest stable release of OpenCover.
When merging multiple results using mergeoutput, if coverbytest is also specified, then the output TrackedMethod elements from each run start with a uid of 1. This causes the uid in the TrackedMethodRef elements to be ambiguous.
This also causes ReportGenerator to crash when reading the resulting report file.
My Framework
My Environment
I have already...
My issue is related to (check only those which apply):
Expected Behavior
The TrackedMethod uid should be unique in a manner similar to the SequencePoint uspid and File uid.
Actual Behavior
The TrackedMethod uid sequence begins at 1 with each run.
Steps to reproduce the problem:
The text was updated successfully, but these errors were encountered: