Could it be that the `--process-execution-local-pa...
# development
c
Could it be that the
--process-execution-local-paralllelism
is a bit aggressive by default, using
#cores
by default? When running the full pants test suite on my laptop, a lot of tests timeout, but when I turn this option down a notch (from the default 12 to 😎 it runs much more smoothly.
âž• 1
ggaahah. why am I not allowed to type
8)
!?
there’re still timeouts, but less frequently.
hmm… but it seems to be getting worse over time… and after breaking out with
<ctrl-c>
I see quite a few number of lingering sleeping python processes from the tests, that I think ought’ve either quit or been killed..
and also a number of
pantsd
:
Copy code
26439   ??  S      0:40.04 pantsd [/private/var/folders/8j/c8jf_msj009947wyw82xvdkw0000gn/T/process-executionSRPx0O]             
26442   ??  S      0:39.83 pantsd [/private/var/folders/8j/c8jf_msj009947wyw82xvdkw0000gn/T/process-executionTXzyPj]        
...