Feature request: add limit on persistent coverage information
See original GitHub issueWe’re running OpenCover and ReportGenerator on each PR and the amount of data is growing to a point it takes a minute plus to parse historical coverage info supplied via -historydir argument.
I propose a set of new arguments that limits how may items are loaded:
-historymax:<maximum items to read>
-prunehistory:<true|false>
– if true, limit file count in historydir
to historymax
, keep newest
I can write the code change and PR back to this repository but would love to get some information on whether this makes sense or any alternative approach that I should write instead.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Test coverage visualization | GitLab
A limit of 100 <source> nodes for Cobertura format XML files applies. If your Cobertura report exceeds 100 nodes, there can be mismatches...
Read more >Storing workflow data as artifacts
Artifacts allow you to persist data after a job has completed, and share that data ... For more information, see "Usage limits, billing,...
Read more >MQTT - AWS IoT Core
Messages are stored according to account limit. Messages that exceed the limit will be dropped. For more information about persistent message limits, see...
Read more >Understanding the Summary of Benefits and Coverage (SBC)
The SBC is a snapshot of a health plan's costs, benefits, covered health care services, and other features that are important to consumers....
Read more >libFuzzer – a library for coverage-guided fuzz testing.
Introduction¶. LibFuzzer is an in-process, coverage-guided, evolutionary fuzzing engine. LibFuzzer is linked with the library under test, and feeds fuzzed ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jatouma: The setting only applies to the number of files that get parsed. When generating the HTML report always a maximum of 100 points in the chart gets rendered.
Why does this make sense?! There are two reasons:
I have not been able to increase the 100 files limit. I have tried changing the value in the config file to 300, but my history report still shows 100 only. Does ReportGenerator not support increasing that maximum value? From skimming through the code, seems like this should work.