Coverage report fails after 65536 characters
See original GitHub issueThe GitHub comment maximum length is, apparently, 65536 characters (though I suspect they might mean bytes):
RequestError [HttpError]: Validation Failed: {"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body is too long (maximum is 65536 characters)"}
Having encountered a coverage report that surpasses this limit, and knowing the repo in question will only continue to have lengthier reports in the future, I’d like to find ways to shorten the report, or possibly split it across multiple comments.
I realize I could resort to an external coverage reporting tool, but I’d prefer to keep everything in one place. (Plus, with private repos, the cost of external tools gets really high really fast.)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:23
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Common Problems | TeamCity On-Premises Documentation
TeamCity reports character set/collation mismatch error: database tables/columns have a character set or collation that is not the same as the ...
Read more >Issues · romeovs/lcov-reporter-action - GitHub
Comments a pull request with the code coverage generated by your tests. ... Coverage report fails after 65536 characters.
Read more >Covid: how Excel may have caused loss of 16,000 test results ...
In 2013, an Excel error at JPMorgan masked the loss of almost $6bn (£4.6bn), after a cell mistakenly divided by the sum of...
Read more >Teamcity 8 + MSTest + DotCover - Not generating coverage ...
The test coverage has been working fine with the same setup and fail to figure out what got updated recently (checked build configuration ......
Read more >Selection of Cyclic Redundancy Code and Checksum ... - FAA
This report explores the characteristics of checksums and cyclic ... would be no guarantee of burst error detection coverage because a 1-bit error...
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
Had same problem, and because it looks like this bug is open for long already I forked and modified it to not send link to every line that was not covered. Feel free to use it:
Also this action failed for me when run on below trigger (it assumes that it is pull request), that was also fixed in my fork.
@mszlgr would you consider create a PR for this change?