I'm seeing process execution sandbox dirs without ...
# development
h
I'm seeing process execution sandbox dirs without
__run.sh
, is that normal?
e
I don't believe so.
h
Can you run with
--no-process-execution-local-cleanup
near current main and see if you reproduce?
I will try and bisect
e
Yup...
h
It may be only specific processes, trying to narrow it down
e
Yeah, I found 5 for 5 in a test run.
Copy code
$ git shortlog -1
Eric Arellano (1):
      [internal] Extract each downloaded Go module (#13094)

$ ./pants --no-process-execution-local-cleanup --no-process-execution-local-cache test src/python/pants/util/strutil_test.py
$ find /tmp -name "process-execution*" -type d | wc -l
22
$ find /tmp -name "process-execution*" -type d | while read d; do ls -l $d/__run.sh; done | wc -l
22
So lgtm. But that's just the test graph.
h
Huh, it only happens in my branch (for https://github.com/pantsbuild/pants/pull/13096) and only when I run
package
on a dist, e.g.,
./pants --no-process-execution-local-cache --no-process-execution-local-cleanup package src/python/pants/testutil/:testutil_wheel
But then it happens for many processes (the setuptools run, but also dep inference and others)
but not all!
And now it doesn't reproduce after merging into main
đź‘€ 1
I give up, will keep an eye out
h
I'm seeing this too now!
h
I saw this over the weekend, I think I had an intuition about it, but now I can't remember what that was
I think maybe it was errors in creating the sandbox dir or something
đź‘€ 1