Thanks!

Hi all, as mentioned on

pants-devel@

, please consider taking our (that is, Toolchain Labs's) survey, if you haven't already: https://www.surveymonkey.com/r/53SCYZ8 Responses from the Pants community will help us prioritize feature development and drive wider adoption, which benefits us all. Multiple responses from the same team/org are fine, so don't worry about who else is responding. Thanks! ~ @happy-kitchen-89482 and @enough-analyst-54434

Any chance someone might be available to nudge the failed CI builds here https://travis-ci.org/pantsbuild/pants/builds/508540611 ? Failures all look to be the same issue (a

403

trying to get the bootstrapped

pants

pex) and not related to the changes in that branch (maybe I need to rebase?)

i think when in doubt rebasing is an approach i apply frequently, i can restart them unless you've tried that already

I don’t have access to be able to restart them myself, though thinking on it more it seems the pexs might not be available anymore so I’ll rebase first and holler back if the issue persists. Thanks!

i've restarted them

they should fail fast so if they fail again i would try rebasing or just a

git commit -n --amend -C HEAD && git push --force-with-lease

your analysis seems correct (that they are probably not related to the branch)

this took many moons but is merged now so we can be less extremely mysterious upon receiving a control-c https://github.com/pantsbuild/pants/pull/6574

how hard would it be to add support for non-junit scala test suites? specifically i’m interested in teaching pants to run tests created using this library https://github.com/lihaoyi/utest

and alternatively, what does it mean to create a

junit_tests

in pants? i could also try to make utest conform to that.

Hi, Is there a way to use

JvmToolMixin.register_jvm_tool

with local build targets? Can I pass local scala target as parameter to classpath_spec?

The problem I am trying to solve is, the jvm tool which I’d like to use in one of custom tasks is also part of the source code. Is there a way to make the task to compile and publish this jar to local repository (under some conditions) and make the custom task use this jvm tool

@loud-guitar-4381 We've done this internally, I don't remember the details, and I'm in the middle of a couple of things now, but ping me in a couple of hours and I'll look up how I did it...

We figured out a way to build a JVM tool and invoke it in a single pants run, and have changes to the tool invalidate the targets it runs on

Hi, is there any documentation regarding converting an existing spring-boot project to pants?

I have a project that is currently built with gradle and uses the gradle spring-boot plugin

running into some issues related to Autowiring/Bean definition

when building with pants

is this a familiar error for folks? hoping to maybe to the stack trace from ‘/usr/local/bin/python’

hi! I’m trying to run pants to test some things, and I’m getting this error:

creating build/temp.macosx-10.9-x86_64-3.7/build
creating build/temp.macosx-10.9-x86_64-3.7/build/temp.macosx-10.9-x86_64-3.7
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -arch x86_64 -g -I/Library/Frameworks/Python.framework/Versions/3.7/include/python3.7m -c build/temp.macosx-10.9-x86_64-3.7/_openssl.c -o build/temp.macosx-10.9-x86_64-3.7/build/temp.macosx-10.9-x86_64-3.7/_openssl.o -Wconversion -Wno-error=sign-conversion

stderr:
no previously-included directories found matching 'docs/_build'
warning: no previously-included files matching '*' found under directory 'vectors'
build/temp.macosx-10.9-x86_64-3.7/_openssl.c:488:10: fatal error: 'openssl/opensslv.h' file not found
#include <openssl/opensslv.h>
         ^~~~~~~~~~~~~~~~~~~~

Has anyone seen it before?

So I'm running in this issue.

## Exception when compiling 44 sources to /data/var/lib/jenkins/workspace/pr-mediarithmics-platform-pants/.pants.d/compile/zinc/a53b6931478d/mediarithmics-api.core-api.src.test.scala.scala/current/classes
                       [error] java.io.IOException: Analysis at (d6aa1af9a111c49918f3f1e79451c82b: /data/var/lib/jenkins/workspace/pr-mediarithmics-platform-pants/.pants.d/compile/zinc/a53b6931478d/mediarithmics-api.common-play-api.src.main.scala.scala/9520fc387886/z.analysis) has changed since startup!

I'm using pants

1.14.0

but I have no idea where to look to solve this error. for a bit of context, we run our tests using the following script

test-changed.sh

has someone already ran in a similar issue ? Not sure where to start to solve it 😕

Hi team, is there an easy way to cache coverage result within pants? I don't know which option to do it.

quick question: We're seeing this warning:

pex: Please build pex with the subprocess32 module for more reliable requirement installation and interpreter execution

. Is this something we just

pip install

locally or is there some way of putting this in a config to always download and use (e.g in

pants.ini

)?

Would anyone happen to use the

StatsDb

bits from

./pants server

(ie. the

Timing Stats

views)? I’m looking into cleaning up some of the json reporting / logic as a followup to the new

JsonReporter

and the schema there is coupled to the current

stats

json output (not a blocker, but if it’s not being used it seems like a candidate for removal).

question about building wheels out of pants targets: I have a python_library target that I want to export as a wheel. it depends on some internal code (python_library targets) which I would like packaged into the wheel, and some 3rdparty deps which I would like to be listed in the wheel’s requirements. when running

./pants setup-py --run=bdist_wheel thing/I/want/a/wheel/for

, I get: “No exported target owner found for PythonLibrary(BuildFileAddress(an/internal/python_library/target/I/depend/BUILD.pants, on))” reading https://github.com/pantsbuild/pants/blob/60197188cb02f7ff60ac723f12780353fb2f2ee9/src/python/pants/backend/python/tasks/setup_py.py#L223, it seems like this shouldn’t be an issue.

thing/I/want/a/wheel/for

does have a provides attribute, and it depends on

an/internal/python_library/target/I/depend:on

, which seems like it should make the former an owner for the latter. am I misunderstanding something?

that code is trying to choose one unique owner for each internal lib

(iirc)