JavaScript heap out of memory

[mpreiner]

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?

[Shylock-Hg]

https://github.com/vesoft-inc/nebula/pull/1596/checks?check_run_id=380846834
Same trouble.

[Shylock-Hg]

I try to increase nodejs memory limit upto 20GB follow this https://support.circleci.com/hc/en-us/articles/360009208393-How-can-I-increase-the-max-memory-for-Node-
but still OOM, it's readlly crazy...

[alexjurkiewicz]

You can use this project to generate lcov and upload it. It works with a project of mine that hits OOM with this node app: https://github.com/eddyxu/cpp-coveralls

[Shylock-Hg]

You can use this project to generate lcov and upload it. It works with a project of mine that hits OOM with this node app: https://github.com/eddyxu/cpp-coveralls

Yes, but the github action now just expose the GITHUB_TOKEN to forked repo PR, the other secrets can't access. This is the main reason why I want to use coveralls action.

[alexjurkiewicz]

If you add a custom secret, you can pass in the coveralls repo key (not GitHub token) as a secret env var.

…

On Thu, 16 Jan 2020, 5:29 pm Shylock Hg, ***@***.***> wrote: You can use this project to generate lcov and upload it. It works with a project of mine that hits OOM with this node app: https://github.com/eddyxu/cpp-coveralls Yes, but the github action now just expose the GITHUB_TOKEN to forked repo PR, the other secrets can't access. This is the main reason why I want to to coveralls action. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#31?email_source=notifications&email_token=AAC4U5IAEGXXOHGKTMDOFDLQ575DRA5CNFSM4J4CC7R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJC562I#issuecomment-575004521>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC4U5JRRYJLH6CDRWGIUNLQ575DRANCNFSM4J4CC7RQ> .

[Shylock-Hg]

If you add a custom secret, you can pass in the coveralls repo key (not GitHub token) as a secret env var.
…
On Thu, 16 Jan 2020, 5:29 pm Shylock Hg, @.***> wrote: You can use this project to generate lcov and upload it. It works with a project of mine that hits OOM with this node app: https://github.com/eddyxu/cpp-coveralls Yes, but the github action now just expose the GITHUB_TOKEN to forked repo PR, the other secrets can't access. This is the main reason why I want to to coveralls action. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#31?email_source=notifications&email_token=AAC4U5IAEGXXOHGKTMDOFDLQ575DRA5CNFSM4J4CC7R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJC562I#issuecomment-575004521>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC4U5JRRYJLH6CDRWGIUNLQ575DRANCNFSM4J4CC7RQ .

I can't understand your reply, in github action CI we can't access the custom secrets from a forked repo PR. How to pass the coveralls repo key?

[sidverma32]

check this answer: https://stackoverflow.com/questions/38558989/node-js-heap-out-of-memory/66914674#66914674