question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature request: add limit on persistent coverage information

See original GitHub issue

We’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:closed
  • Created 7 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
danielpalmecommented, Aug 28, 2018

@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:

  • A chart with (many) more points in not readable any more, that’s why a fixed limit exists here
  • Parsing more files can make sense if you perform many build with little changes. The charts only contain points when there was a change in:
    • number of covered/total lines
    • number of covered/total branches
0reactions
jatoumacommented, Aug 28, 2018

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.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found