Over the weekend, two memory intensives jobs were built at the same time. This lead to the linux kernel killing the process in the build step

Jenkins didn't seem to notice that was what happened, leading the the job hanging. Looking at the list of active processes (using ps -ef | grep jenkins) Jenkins didn't have any processes doing anything from what I could tell.

As far as I can tell, pipeline should have seen the fact the subprocess has been terminated?