Hi, Happy new year guys. I have a question about pant’s

tag

. for example we have below test definition with tags :

target1(…,tag=integration-test), target2(…,tag=unit-test-team1), target3(…,tag=unit-test-team2), …

Then for simple we created an aggregation target:

targetAll(dependencies=[target1,target2,target3,…])

we thought we can filter out ‘integration-test’ from all tests by using

./pants test targetAll --tags=-integration-test

However, target1 is still executed, so we thought the filter on

tag

will not work with the sub targets. do you have any recommendations about how

tag

should be used in this situation?

I was trying to force a test to fail but still passed, even with

--cache-test-junit-ignore.

Anything changed recently, e.g. additional layer of caching? https://gist.github.com/wisechengyi/d4bd03691395d5037ca5913aec45de1e#file-gistfile1-txt-L20-L24

"assert false" is a java assertion rather than a junit assertion

they are not enabled by default

Hi, I'm on pants 1.16. Is there a way to specify default options on the command line?

./pants --jvm-options="-Xmx1g" options | grep shader.jvm_options
shader.jvm_options = ['-Xmx256m', '-Xmx3g', '-XX:+UseParallelGC'] (from CONFIG_DEFAULT in pants.ini)

https://www.pantsbuild.org/options.html#command-line-flags mentions its possible for global options, but I guess not default options?

On Chrome79, none of the option names are showing up on https://www.pantsbuild.org/options_reference.html. Just the default value and the description

How do I disable timeouts in pants when running pytest. I’m trying to use pdb inside a test. neither

--timeout

or

--test-pytest-timeouts=False

seems to help

I’m doing some work around making it easier to have targets that want different runtime platforms. This is some refactoring / consolidation work that moves towards making those changes easier. https://github.com/pantsbuild/pants/pull/8938

@witty-crayon-22786 ^^

Hey all, qq, is there any way to suppress specific warnings from the pants output. There are some deprecation warnings we have in packages i,e:

DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses.

And hoping to clean up the output a bit so it isn't as noisy. Has anyone run into this before?

which version of pants is that?

Thoughts appreciated on issue around ConsolidateClasspath and ClasspathEntry ordering: https://github.com/pantsbuild/pants/issues/8941

I have a python_library with

compatibility="CPython>=2.7,<3"

and it depends on python requirement

more-itertools

(no version provided). Pants will install the latest version of

more-itertools

despite it is not compatible with Python 2.7. This is expected behavior for version 1.12? (I know I can pin the version but would like to confirm my observation)

Any good suggestion on testing python target in parallel?

I’d like to deprecate a field in export, with the intent of removing it later, specifically,

test_platform

. I could add a deprecate conditional call in export, but I’m not sure if that’s the right approach, because it might be noisy. Alternatively, we could just leave it in until there’s more needed changes to export, and remove it as part of doing that.

How much do we care about new users being able to use Pants 1.16 and earlier? If we’re okay with dropping that support, we’d be able to simplify our setup

./pants

script that we distribute to uses. Note that only new users or prior users who explicitly re-download the script would be impacted.

Personally I don't think we should want new users on antique versions, and if they absolutely must then we can work with them on a custom script

Hey guys I'm trying to modify pants bootsrap dir , but it doesn't seem to be working ?

[GLOBAL]
pants_version: 1.24.0.dev2
print_exception_stacktrace: True
pants_bootstrapdir: '%(buildroot)s/.cache/pants'
pants_configdir: '%(buildroot)s/.config/pants'

There is a little bug with

local_store_dir

is

v1.24.0.dev2

. when setting the local_store in pants.ini, it should be set without the ' ', because otherwise, it creates a folder with ' in the name, example:

[GLOBAL]
pants_version: 1.24.0.dev2
print_exception_stacktrace: True
pants_bootstrapdir: '.cache/pants'
pants_configdir: '.cache/pants/config'
local_store_dir: '.cache/pants/config/lmdb_store'

will create a folder named

'.cache

with subsequent subfolders

local_store_dir: .cache/pants/config/lmdb_store

fixes the issue

Is there any good guide on BUILD file optimization? a recent change i made has been causing a lot of

duplicate file

warnings

hi there, is there a way to find the BUILD file that owns a given file?

./pants filemap

doesnt return anything for me

How would I access options defined on a GoalSubsystem subclass from logic implemented in a Subsystem class (specifically the one we use as a streaming_workunits_handlers) ? I just need the option values, not the instance of the GoalSubsystem subclass itself. @hundreds-father-404 @hundreds-breakfast-49010

hello! as we are working in mixed py2 and py3 env, is it possible to tell repl to mixed with different ipython versions ?

ipython_requirements: ['ipython~=5.8.0; python_version<3']

?

Hello all, I am trying to move my project to pants. We are using a private repo (cloudrepo) for some of our python packages. I tried to point to this repo having the credentials in the URL, but it looks like pants is ignoring them I filed an issue, but I wonder if you guys can give me some pointers? https://github.com/pantsbuild/pants/issues/8971 running

./pants -ldebug binary src/target

shows a mix of HTTP 200 and HTTP 401 replies from cloudrepo:

17:32:43 [DEBUG] urllib3.connectionpool:pid=80884: <https://xxxx.mycloudrepo.io:443> "GET /repositories/prod/test-lib/ HTTP/1.1" 200 1029
17:32:43 [DEBUG] urllib3.connectionpool:pid=80884: <https://xxxx.mycloudrepo.io:443> "GET /repositories/prod/test-lib/test-lib-0.1.0rc2.tar.gz HTTP/1.1" 401 52

This removes the

generate-pants-ini

goal, see PR description for why I think that's right: https://github.com/pantsbuild/pants/pull/8993 Posting here in case it's controversial.

How can I turn off pip progress bars in pants build?

it really pollutes the logs

is --test-pytest-options not supported anymore?

I'm getting

ERROR: Unrecognized command line flags on scope 'test.pytest': --options.

(Use --print-exception-stacktrace to see more error details.)

pants versions:

1.23.0

Trying to run unit test with

compatibility="CPython>=2.7,<3"

and start seeing issues like this today:

Failed to execute PEX file, missing linux_x86_64-cp-27-cp27mu compatible dependencies for:
                     importlib-metadata
                     zipp

With verbose:

pex: Failed to resolve a requirement: The 'zipp>=0.5' distribution was not found and is required by importlib-metadata
                     pex: Activating PEX virtual environment from /home/zxiong/cruise/mlp-ark/.pants.d/test/pytest-prep/CPython-2.7.15/88508bc93f076e9344b70c0dbc1c3bca526914f7 :: Resolving unittest2>=1.1$0; python_version < "3"
                     pex: Unresolved requirements:
                     pex:   - importlib-metadata
                     pex:   - zipp
                     pex: Distributions contained within this pex:
                     pex:   - more_itertools-5.0.0-py2-none-any.whl
                     pex:   - pathlib2-2.3.5-py2.py3-none-any.whl
                     pex:   - configparser-4.0.2-py2.py3-none-any.whl
                     pex:   - six-1.14.0-py2.py3-none-any.whl
                     pex:   - pytest_mock-1.10.4-py2.py3-none-any.whl
                     pex:   - argparse-1.4.0-py2.py3-none-any.whl
                     pex:   - linecache2-1.0.0-py2.py3-none-any.whl
                     pex:   - py-1.8.1-py2.py3-none-any.whl
                     pex:   - scandir-1.10.0-cp27-cp27mu-linux_x86_64.whl
                     pex:   - zipp-0.0.0-py2-none-any.whl
                     pex:   - coverage-5.0.3-cp27-cp27mu-manylinux1_x86_64.whl
                     pex:   - traceback2-1.4.0-py2.py3-none-any.whl
                     pex:   - flaky-3.6.1-py2.py3-none-any.whl
                     pex:   - funcsigs-1.0.2-py2.py3-none-any.whl
                     pex:   - atomicwrites-1.3.0-py2.py3-none-any.whl
                     pex:   - pluggy-0.13.1-py2.py3-none-any.whl
                     pex:   - contextlib2-0.6.0.post1-py2.py3-none-any.whl
                     pex:   - wcwidth-0.1.8-py2.py3-none-any.whl
                     pex:   - importlib_metadata-1.4.0-py2.py3-none-any.whl
                     pex:   - unittest2-1.1.0-py2.py3-none-any.whl
                     pex:   - pytest-4.6.9-py2.py3-none-any.whl
                     pex:   - attrs-19.3.0-py2.py3-none-any.whl
                     pex:   - mock-3.0.5-py2.py3-none-any.whl
                     pex:   - packaging-20.0-py2.py3-none-any.whl
                     pex:   - pytest_timeout-1.3.4-py2.py3-none-any.whl
                     pex:   - pyparsing-2.4.6-py2.py3-none-any.whl
                     pex:   - pytest_cov-2.8.1-py2.py3-none-any.whl

Note that the included zipp version is zipp-0.0.0-py2-none-any.whl zipp released version 2.0.0 2 days ago which only supports python 3. Could this be related? Any recommendation for how to do further investigation?