> We had understood that once the timer starts ...
# development
w
We had understood that once the timer starts for an
ExecuteProcessRequest
, it already has a slot in the worker pool and does not ever have to yield its CPU time to other processes. This might not actually be the case?
the relevant code is here: https://github.com/pantsbuild/pants/blob/121ec6f78aa8338f101e3dac75b3d52006eed44f/src/rust/engine/process_execution/src/remote.rs#L181-L253