Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U098ZNTCN> mem got better after rebase while runtime regressed:

```master
RSS=3.4GB
real    8m9.703s
user    8m16.123s
sys     0m31.198s

pr4349
RSS=3.4GB
real    11m30.371s
user    11m35.113s
sys     0m30.440s

```

at least now we only need to explain the perf and there is a theory

...i have a sinking feeling that the deadlock may not be resolved. keep an eye out for runs that just hang with no cpu usage =/

might be seeing the deadlock in CI w/ the v2-by-default branch rebased - 3 instances of `No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.` on random tests :grimacing:

i saw the same on one shard of master. damn.

blargh... no repros during any of the rebases i did of that branch.

well, lots more surface area with v2 by default

could fix forward if you’d like, given it’s v2 specific - we can defer landing v2-by-default a bit

nah... i saw in it master as well. and i think i had a local repro.

(you can see why i was so bummed to have to work around this before vacation!)

```[== 00:00 Bootstrapping pants ==]
00:39:47 00:00 [main]
               (To run a reporting server: ./pants server)
00:39:47 00:00   [setup]
00:39:49 00:02     [parse]

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: <https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received>```

that seems to indicate it stalled out in the post-v2 path?

(ie, will just let a `while true` spin in the background.)

seeing other network related stuff - bintray timeouts and such

will kick off another build tonight to try to independently verify