- changed status to open
- removed comment
ignore auto-generated code in coverage analysis
Issue #1592
closed
The Cactus build process auto-generates some glue code in bindings which clutters the coverage analysis. Similarly ExternalLibraries contain code that we don't ourself maintain.
I may be useful not to include these codes in the coverage analysis.
The attached patch does so by inspecting the directory to be processed when generating the results page.
Is this a desirable feature and an implementation that is acceptable?
Keyword:
Comments (4)
-
reporter -
- changed status to open
- removed comment
Looks good to me.
-
reporter - changed status to resolved
- removed comment
Applied as rev 764 of Utilities.
-
reporter - edited description
- changed status to closed
- Log in to comment