I am getting some issues with an action that runs
dotnet build in our project; sometimes the dotnet command returns exit status 143, and all I see in the output of the command is normal build messages, nothing from stderr at all.
I have verified the dotnet command reaches close to 2GB RAM during a build, and the behavior really looks like the process is killed by OOM Killer or the virtual instance’s hypervisor. But with just a 2GB RAM footprint should be way behind the threshold.
Anybody else having processes killed by the system on actions run? I believe
dotnet may be receiving SIGTERM (15) and it returns exit status 128+signal, and I see some docker topics related to this, but I am not running the action under a Docker Container (not explicitly at least).