I'm not using pex atm, however, Wickman's recent land of Mark Abramowitz's bdist_pex

may make this easier to support

QQ: we are having problems with one of our custom plugins randomly exiting with non-zero status (as if a TaskError was thrown). When I try to debug it with a development version of pants, I can’t reproduce it. Did something change? recently? The production version is running from a pex.

The only change near there was ... just a sec - @rough-minister-58256 fix

a task you mean?

@witty-crayon-22786: Yes, a task

Pants uses 1.0.3 on HEAD but not in 0.0.41 - goes out with today's release - so likely notit

and his change is deterministic

@ancient-stone-50795: is the underlying tool exiting, or the python code in the task? and

--print-exception-stacktrace

doesn't show anything?

@ancient-stone-50795: oh! also, check

./pants server

I’m not sure if I’ve caught it with —print-exception-stacktrace

it might be a background task dying

if a background task dies, you'll exit 1

Here’s another interesting tidbit - it fails in the configuration where we have the read/write artifact caches turned on.

./pants clean-all test script:test --config-override=pants-ci.ini 
…

12:47:25 00:03     [rspecs]
                   Bundler setup
                   Checking if bundle is installedWARN] /Users/zundel/.pex/install/requests-2.5.3-py2.py3-none-any.whl.ed9d28acc3c467062b25b9dc2e2084d6efa8ee1e/requests-2.5.3-py2.py3-none-any.whl/requests/packages/urllib3/connection.py:251: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See <https://github.com/shazow/urllib3/issues/497> for details.)
  SecurityWarning


                   Running specs
                   Finished in 2.61 seconds (files took 0.23828 seconds to load)
                   33 examples, 0 failures
               Waiting for background workers to finish.
12:47:30 00:08   [complete]
               FAILURE

@ancient-stone-50795: yea, definitely the background task then.

$ cat pants-ci.ini
[DEFAULT]
colors: False

[cache]
read_from: ["<https://pypi.corp.squareup.com/laundrybasket-rw/>"]
read: True
write_to: ["<https://pypi.corp.squareup.com/laundrybasket-rw/>"]
write: True

Otherwise, it doesn’t fail

look at

./pants server

There is no ouptut from the run in pants server

er

have you run it since your last clean-all?

or are you saying that the server is broken?

My repro is

./pants clean-all test script:test --config-override=pants-ci.ini

I’ll run clean-all separately

yea

Screen Shot 2015-08-14 at 12.51.06 PM.png

yep

Not this is it?: https://github.com/pantsbuild/pants/issues/929

Seems unlikely

Possibly, I don’t see anything actually making it into the cache recently.