<@U06A03HV1> and I have been DMing about an issue ...
# development
@witty-crayon-22786 and I have been DMing about an issue with timeouts when running V2 remoting.
build-support/bin/ci.py --python-tests-v2 --remote-execution-enabled
has both times I’ve tried resulted in a timeout like this:
Copy code
Exception: Failed to execute process: Exceeded time out of 900s with 900.626410638s for operation projects/pants-remoting-beta/instances/default_instance/operations/EAEaGGZvdW5kcnktOTE2NzI0N2JjNzQ2N2EwNyIGYWN0aW9u, Run pytest for tests/python/pants_test/backend/python/subsystems:python_setup
But when running that test directly, it only takes 15 seconds to run: https://pantsbuild.slack.com/archives/C0D7TNJHL/p1563397967017800?thread_ts=1563397846.017500&amp;cid=C0D7TNJHL We had understood that once the timer starts for an
, 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?