When a pex build gets stuck (spinning on

Building N requirements for Y.pex

), is there a way to interrogate what requirement is jamming it up? It seems like it'll happily "build" forever without making any progress.

I use to do a

ps ax | grep pants

which will show you running processes and one of them likely has a tmp path with interesting log files to tail during a run… 😉

and if it actually finishes, you can use

--pex-verbosity=3 -ldebug

or higher to get some more info on where time was being spent, i think?

Well it'll definitely finish once I ctrl+c it, so I can try that next time!