How can I debug a long-running .pex build process that I suspect is due to some auth/network issues? Setting

PANTS_LEVEL=debug PANTS_PEX_VERBOSITY=9 PIP_VERBOSE=3

doesn’t provide any additional logging output from these sections:

15:11:18.39 [INFO] Long running tasks:
  265.86s	Building .ci.package.pex with 1 requirement: PyYAML==6.0
15:11:48.42 [INFO] Long running tasks:
  295.90s	Building .ci.package.pex with 1 requirement: PyYAML==6.0

If you run with

--keep-sandboxes=always

to make it leave a sandbox behind, you can then go into the sandbox and run the

__run.sh

file directly. This might get more logs out (ie. avoid pants capturing of logs). You can also edit the

__run.sh

file to potentially turn on more verbose logging of whatever individual tools are running in that task)

Bit tricky since the issue I’m seeing only crops up in our CI jobs where the auth/resources are different.

hmm, yeah that does make it tougher.