coverallsapp / coverallsapp/github-action
JavaScript heap out of memory
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
I'm running into an out of memory problem in a larger C++ project (https://github.com/mpreiner/CVC4/runs/351674288). I checked the size of the lcov.info on my machine an it's 95M. The 2048M heap limit seems to be a limitation from node. Is there a way to increase the heap limit for the coveralls action so that it uses all the available memory of the runner?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how this GitHub Action invokes Node and processes the lcov.info file, using the linked CVC4 workflow run as the reproduction context. Determine whether the heap limit can be increased for the action, and consider the issue done when a 95M coverage file completes without the JavaScript heap out-of-memory failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions, node.js
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100