I am running jest tests inside a docker container on github actions which used to run well until last commit and since then, it always exits with 137
> jest --coverage Error: Process completed with exit code 137.
Not sure if this is docker exiting with 137 or jest inside docker. But on linux machines, the memory limit of a docker container is the same as memory of the host, there is no fine tuning like in docker for mac or docker for windows. And there hasn’t been added anything in the last commit that could eat up all the memory.
Searching this forum, didn’t find any post about anything related to exit code 137.
I am not finding any docs arround specs of github action runners, how much memory do they have? Not sure how to debug this. Any suggestions?