Open csiefer2 opened 1 week ago
Hi @csiefer2. Yes, this can happen with large C/C++ projects. coverage-reporter, which underlies our github-action, can process however many coverage report files you have in your environment, but above a certain number will lead to a timeout.
Our recommendation here is to use gcov
to generate a single lcov
report for your project (or at least fewer reports).
You can find steps to do so in these blog posts / tutorials:
By default, your lcov
file will be exported as coverage.info
, so if you think you'll have any extraneous or duplicate files in your environment, we additionally recommend that you specify at least the format
, and ideally, the file
as well.
format and file can be passed as a flag, and an argument, respectively, in the command line command for coverage-reporter, like this:
coveralls report coverage/coverage.info --format=lcov
For the github-action, you'll want to add those two input options, under with:
, like this:
- name: Coveralls Coverage Report Upload
uses: coverallsapp/github-action@v2
with:
format: lcov
file: path/to/coverage.info
What was wrong?
I'm using coveralls through a github action. There are probably about ~50k gcov files that our testing generates.
We get finish the file processing and then this happens:
Logs
Coveralls version: v0.6.12