Search Issue Tracker
Fixed
Fixed in 1.2.6
Votes
0
Found in [Package]
1.2.5
Issue ID
COV-46
Regression
No
Code Coverage package does not report some of the internal ReportGenerator errors
Steps to reproduce:
Implementations of DebugLogger.Debug(), DebugLogger.Info(), DebugLogger.Warn() and DebugLogger.Error() do not print logs passed to them.
This is usually not an issue as internally in most places ReportGenerator is using Format() variants (DebugFormat(), WarnFormat(), etc), which do print logs they receive. However, when an exception occurs in [https://github.com/danielpalme/ReportGenerator/blob/v5.0.4/src/ReportGenerator.Core/Generator.cs#L151] catch block calls Error(). Because of that, exceptions that occur inside report generator aren't surfaced back to the editor and users cannot investigate the cause of a failure.
Actual results:* No error when exception occurs in the Report Generator
Expected results: Editor console displays the error that Report Generator has encountered
Reproducible with versions: 1.2.5
Notes:
- No repro steps, as I couldn't get report generator to throw an exception, however, issue should be clear by looking at the code.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Broken hyperlink formatting in HDRP 3D Sample Tutorials
- Missing spaces in High Definition 3D Samples Template Tutorials
- Win64 CPU is set to None when applying changes to plugin where the meta has the serializedVersion 2
- Sprite Atlas textures from all included build scenes persist in Editor memory when building the Player
- Disabling all columns in Light Explorer throws “ArgumentException” error in the Console window
Add comment