[cbuild] should listen to signal and terminate appropriately when receiving `SIGTERM`

[acabarbaye]

we are running the cbuild using subprocesses or in containers and so, we make use of unix signals to control the tool (e.g. use of timeout, https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination,etc.). Nonetheless, the tool does not listen to unix signals (such as https://gobyexample.com/signals) and spawns or opens resources such as subprocesses, files, etc. If the tool process receives a SIGKILL, it will hence, most likely, leave resources in a bad state (e.g. open file, hanging subprocesses)

A solution to this would be to ensure the tool listens to signals such as SIGTERM and properly closes any open resources when such signal is received (in other words, it should close gracefully). The use of context could be leveraged.

[soumeh01]

Thank @acabarbaye for bringing up this issue. I'm eager to tackle it, but first, I need to grasp all the details, understand the affected areas, and consider the testing efforts.
Could you please let me know if this issue is critical and blocking you?

[acabarbaye]

hello @soumeh01, in our case we have put things in place to kill any process and their children and I guess we managed to unblock ourselves (i.e. tool does not hang anymore and we do not end up with orphan or zombies processes), although our workaround is a bit radical and could leave the environment in a precarious state. The suggestion was more for end users of the tools such as CI systems, etc, using environments such as kubernetes pods/containers, which may not be aware of the behaviour