Closed taltcher closed 2 years ago
also having this issue
looks like it fails to run npm install --legacy-peer-deps
It should be fixed by #72
So I just ran into a seemingly similar issue (very similar trace). Do we know if this has been fixed in the latest release?
--- Last few GCs ---> 20 21 [19:0x7f59ca327330] 204359 ms: Mark-sweep 2028.7 (2092.3) -> 2017.1 (2094.3) MB, 3426.6 / 9.8 ms (average mu = 0.283, current mu = 0.110) allocation failure scavenge might not succeed 22 [19:0x7f59ca327330] 209106 ms: Mark-sweep 2025.1 (2094.3) -> 2021.0 (2108.5) MB, 4580.1 / 9.8 ms (average mu = 0.157, current mu = 0.035) allocation failure scavenge might not succeed 23 24 25 <--- JS stacktrace ---> 26 27 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 28 Aborted (core dumped) 29 /entrypoint.sh: line 13: /github/workspace/node_modules/.bin/eslint: not found 30 /entrypoint.sh: line 28: /github/workspace/node_modules/.bin/eslint: not found 31 2021/11/12 16:39:50 [eslint] reported: https://github.com/gitglacier/peak-front/runs/4192186866 (conclusion=success)
I ran into a similar issue and used the node_options
to increase the memory limit for my package.json
scripts. That is why I created a pull request #119 which allows you to set the node_options
environment variable for eslint.
merged #119
During our PR workflow, we are receiving:
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
This is the GitHub hook we have created:
This is the full log we receive during the workflow run:
What can cause this issue?