[issue44360] test_compile killed by SIGKILL on AMD64 Ubuntu 3.x (Linux OOM Killer)

Change by Pablo Galindo Salgado : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue44360] test_compile killed by SIGKILL on AMD64 Ubuntu 3.x (Linux OOM Killer)

Senthil Kumaran added the comment: > Maybe you should give more memory to your worker, or you should spawn less > jobs in parallel It was related to high number of jobs in that particular agent and result in OOM Kill from the Linux kernel - https://pastebin.com/559H4ksa The machine has

[issue44360] test_compile killed by SIGKILL on AMD64 Ubuntu 3.x (Linux OOM Killer)

STINNER Victor added the comment: > Yes, this was related to the Linux OOM Killer. Oh ok. Maybe you should give more memory to your worker, or you should spawn less jobs in parallel (-j1 instead of -j2). Or you should disable other services which eat memory. How much memory does it have?

[issue44360] test_compile killed by SIGKILL on AMD64 Ubuntu 3.x

Senthil Kumaran added the comment: Yes, this was related to the Linux OOM Killer. The agent went down shortly after this. Either multiple parallel jobs might have led to OOM or something else. I will see if logs provide more information. -- ___

[issue44360] test_compile killed by SIGKILL on AMD64 Ubuntu 3.x

STINNER Victor added the comment: Oh right, exit code -9 means killed by SIGKILL, it doesn't not mean killed SIGSEGV. Sorry about the confusion. How can a signal be killed by SIGKILL? Can it be related to Linux OOM Killer? Senthil: Would you mind to have a look at the server logs to see if