One of our basic tests is failing on v2.1.1. When I run

pants list ::

it exits with status 1. When I do

for p in $(fd -t d -d 1 .) ; do echo $p ; ./pants list ${p}:: ; done

(i.e. for every directory run,

.pants list ${DIRNAME}::

) and also

.pants list :

I get a list of directories and it exits with status 0. I have print stack trace set to to true and also ran with

-ldebug

. No additional output was provided. Help with debugging would be appreciated.

Hi Raúl, sorry for the trouble. Someone will look into this ASAP, but probably not until tomorrow, due to the new years holiday

No hurry. Happy to help diagnose whenever

Do you have any pants_ignore_warnings filters set?

d'oh! Looks like we prematurely added

ignore_pants_warnings = [".*"]

. Removing that gives me the errors. It looks like 2.1.1 better respects that setting than 2.1.0. Is this worth mentioning on https://www.pantsbuild.org/docs/release-notes-2-1 ?

np. it was this one:

Bugfixes

    Fix filtering of log messages generated in native code. (cherrypick of #11313) (#11316) PR #11316

I’m confused why this is causing an exit code of 0, though? Deprecations shouldn’t impact the exit code

It was a non-zero exit code because of an unrecognized target:

python_binary

. 2.1.0 showed the error (even with the aggressive ignore), but 2.1.1 just exits with code 1, no output.

Ahh, cool, so that’s an expected error. Thanks!