Fixed issue with ReportGenerator.Core when using .NET Core 3.1 #696
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -111,7 +111,7 @@ public void SelectionStatements_If() | |||
| CoverageResult result = TestInstrumentationHelper.GetCoverageResult(path); | |||
|
|
|||
| // Generate html report to check | |||
| // TestInstrumentationHelper.GenerateHtmlReport(result); | |||
| TestInstrumentationHelper.GenerateHtmlReport(result); | |||
|
|
|||
There was a problem hiding this comment.
Can you revert changes to this file?I'll merge package upgrade, it's ok commented, it's so as "documentation" for debugging! Thanks a lot for the fix the integration of your tool is invaluable help for me during coverage bug debugging!
|
Sure. Will revert the change tomorrow. |
|
Failure unrelated, flaky test I'll fix it. |
|
Updated and tested here #698 I'll close this!Thank's a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed issue with ReportGenerator.Core when using .NET Core 3.1 (see #694)