<#12313 `--no-process-execution-local-cleanup` eff...
# github-notifications
c
#12313 `--no-process-execution-local-cleanup` effect sticky after removing the flag from the cmd-line Issue created by benjyw I can't reproduce this, but saw the following behavior: 1. Ran pants with
--no-process-execution-local-cleanup
. 2. Ran pants without that flag. Got:
Copy code
$ ./pants test src/python/pants/backend/python/goals/setup_py_test.py 
23:34:52.37 [INFO] preserving local process execution dir `"/private/var/folders/q4/pv4jnnm944b_ywr3tnp_b1300000gn/T/process-executionO2SA7S"` for "Test binary /Users/benjyw/.pyenv/shims/python."
23:34:52.37 [INFO] preserving local process execution dir `"/private/var/folders/q4/pv4jnnm944b_ywr3tnp_b1300000gn/T/process-executionvPyM1p"` for "Test binary /Users/benjyw/.pyenv/shims/python3."
23:34:52.37 [INFO] preserving local process execution dir `"/private/var/folders/q4/pv4jnnm944b_ywr3tnp_b1300000gn/T/process-executionbxV4ms"` for "Test binary /Users/benjyw/.pyenv/shims/python2."
23:34:52.46 [INFO] Initialization options changed: reinitializing scheduler...
23:34:53.61 [INFO] Scheduler initialized.
23:34:53.61 [INFO] preserving local process execution dir `"/private/var/folders/q4/pv4jnnm944b_ywr3tnp_b1300000gn/T/process-executionfQjjAZ"` for "Test binary /Users/benjyw/.pyenv/shims/python."
23:34:53.61 [INFO] preserving local process execution dir `"/private/var/folders/q4/pv4jnnm944b_ywr3tnp_b1300000gn/T/process-execution8seHIZ"` for "Test binary /Users/benjyw/.pyenv/shims/python2."
23:34:53.61 [INFO] preserving local process execution dir `"/private/var/folders/q4/pv4jnnm944b_ywr3tnp_b1300000gn/T/process-execution1LMzBf"` for "Test binary /Users/benjyw/.pyenv/shims/python3."
23:35:13.18 [INFO] Completed: Building pytest.pex with 6 requirements: ipdb, pygments, pytest-cov>=2.10.1,<2.12, pytest-html, pytest-icdiff, pytest>=6.0.1,<6.3
23:35:17.27 [INFO] Completed: Resolving 3rdparty/python/constraints.txt
<snip> # No further process execution dirs were preserved.
Reran the command, same thing (minus the scheduler reinitialization): The shim-testing processes had their local execution dir loudly preserved. Killed pantsd. Reran the command, which now no longer exhibited the behavior. Wondering if this is due to the native client. pantsbuild/pants