cancellation_manager.pause_all_work() is insufficient to pause work about ml-compiler-opt HOT 3 OPEN

does this happen if we always make sure pause_all_work is followed by resume_all_work?

from ml-compiler-opt.

Yes- say the worker python thread is not waiting on a sub process clang, and at that moment pause all work is executed, no clangs are paused, then the worker is free to start sub process clangs going forward. Resume all work would either be a nop or send a SIGCONT for an already running process

from ml-compiler-opt.

randomly thought of something less race-y, so before I forget: we could have pause_all_work SIGSTOP itself while holding a process-creation-lock right before calling resume_all_work, so the parent process can "call" resume_all_work by sending a SIGCONT

from ml-compiler-opt.