GitHub Community
Ubuntu-latest, dotnet command exiting with status 143 #26620
-
|
I am getting some issues with an action that runs 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 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
I have added dmesg output when it fails, and get no OOM message. This may be related with a bug in the Anyway, I have implemented a code to retry (at most 3 times) the command whenever it fails and it is, consistently, failing the first time I build a project, then works once I retry. Once for every build. So still, problem not solved. |
Beta Was this translation helpful? Give feedback.
-
|
Turned out I had a timeout set to I had no clue as there was no error on stderr and the |
Beta Was this translation helpful? Give feedback.
Turned out I had a timeout set to
spawn()call from a Node JS script which fired thedotnetcommand. As the timeout was reached, Node JS sent the CLI aSIGTERM(15) signal, then it returned with that 128+15=143 exit status.I had no clue as there was no error on stderr and the
Errorreturned was being ignored by the script. The issue just happened cause our project grew big enough to exceed the timeout. Increasing the timeout resolved the issue.