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

Pants

to be clear, it was non-deterministic when the interpreter wasn't bound

we should be on 0.0.39 now (that sha is 0.0.39), but can try moving closer to head

1st things 1st, I still assume you're getting PEX_VERBOSE logs for before/after or non-deteministic works vs always fails

The algorithm would be - look for a difference -&gt; if a thrift egg/whl difference, crack open these and compare - missing files, missing namespace packages? also compare chroot contents that are loose - any loose thrift files or else thrift packages with no namespace package?

The only other obvious variable would be thrift version - did you keep apache thrift pinned low, as Paul ended up doing above earlier today?

but that would not be flaky across python2.7.x either

`DEBUG] Selected thrift binary bootstrapped to: /Users/stuhood/.pants.d/bin/thrift/mac/10.9/0.5.0-finagle/thrift`

K - PEX_VERBOSE comaprison / chroot comparisons are in-order then

(gathering that stuff... will put in an issue.)

I'll be right back - need to reboot to pick up 4.1.3 kernel - yay!

On that debug statement above - same deal as with Paul - its not a relevant log line for the python backend, only for ApacheThriftGen

So, you may have the version globally set or you may just have it set for ge.thrift , ie: ApacheThriftGen

will see if i can find similar during `gen`

Instead you might just quash all doubt by setting [thrift-binary] version if not already done at the global level

then check ~/.cache/pants/bin/thrift for 0.9.2

it will come back when you run open source pants, but this is a good test for now just using twitter pants_internal

<@U04S45AHA>: looks like it goes to `~/.pants.d/bin/thrift`

OK - ruled out - good, so I'll take a look at that issue with logs then when you post.  If you can do the before after debug steps and include any of that extra data too that would be great.