https://pantsbuild.org/ logo
Powered by
#general
  • b

    brief-engineer-67497

    11/02/2018, 11:22 AM
    The error message mentions updating assets "Exception in thread "main" java.io.IOException: PUT operation to URL https://my-nexus.com/repository/releases-sandbox/com/foo/pants/play-gen-tools/0.0.113/jars/play-gen-tools.jar failed with status code 400: Repository does not allow updating assets: releases-sandbox" however I use 
    ./pants publish pants-plugins/scala/play-gen-tools --no-publish-jar-dryrun --no-publish-jar-commit --no-publish-jar-prompt -ldebug --publish-jar-override=com.foo.pants#play-gen-tools=0.0.113
    And I change the overrided version for each test
  • b

    brief-engineer-67497

    11/02/2018, 11:22 AM
    it's as if it was trying to publish the same artefact twice in a run
  • a

    alert-addition-34873

    11/02/2018, 1:21 PM
    It seems to work with python tests but not scala 😕 I will file issue later today.
  • b

    brief-engineer-67497

    11/02/2018, 1:25 PM
    found It !
    🎉 1
  • b

    brief-engineer-67497

    11/02/2018, 1:26 PM
    A resolver was missing to resolve my dependencies >_<
  • e

    enough-analyst-54434

    11/02/2018, 3:42 PM
    Ah, yes, that is a python (test.pytest) specific option. We don't have the feature for junit (test.junit).
  • a

    alert-addition-34873

    11/02/2018, 4:54 PM
    ohh, that is disappointing. Is there a plan to implement it anytime soon?
  • a

    alert-addition-34873

    11/02/2018, 4:55 PM
    btw the option name is confusing in that case as I thought it will support both as it has both pytest and junit in name
  • e

    enough-analyst-54434

    11/02/2018, 4:56 PM
    No. But this is exactly where you come in. File a feature request issue to start so it's on the radar. Then, potentially, dive in if we don't get to it quickly enough.
    👍 1
  • e

    enough-analyst-54434

    11/02/2018, 4:59 PM
    AH, yeah - agreed somewhat. The option scoping is regular but mysterious. When you say 
    test
    , that implies test tasks for a whole bunch of languages Pants supports (try 
    ./pants --explain tests
    ). So, for example, test.pytest and test.junit. The former tests python code, the latter jvm code using the junit runner. Options are scoped to goal, task. So --test-pytest means this is an option bound for the 
    pytest
    task in the 
    test
    goal. The rest, junit-xml-dir - is the actual option name.
  • e

    enough-analyst-54434

    11/02/2018, 5:00 PM
    ./pants test.junit --help
    and 
    ./pants test.pytest --help
    give scoped help for example.
  • e

    enough-analyst-54434

    11/02/2018, 5:03 PM
    And, fwiw - you can shorten options on the cli leveraging this. To the right of a task you can supply its options in short form; ie: 
    ./pants test.pytest --no-timeouts --junit-xml-dir=./bob [targets]
    .
  • e

    enough-analyst-54434

    11/02/2018, 5:03 PM
  • a

    alert-addition-34873

    11/02/2018, 5:15 PM
    I knew a bit about that (tried to write a plugin once) but still finding it confusing sometimes. Thanks for help.
  • w

    witty-crayon-22786

    11/02/2018, 6:19 PM
    @happy-kitchen-89482: do you remember why we don't render the entire 
    Task/Goal
    docstring in 
    ./pants help $goal
    ? 
    filter
    in particular would be useful: https://github.com/pantsbuild/pants/blob/master/src/python/pants/backend/graph_info/tasks/filter.py#L19-L29
  • h

    happy-kitchen-89482

    11/02/2018, 6:27 PM
    I don’t think there’s a reason
  • h

    happy-kitchen-89482

    11/02/2018, 6:28 PM
    I think it was an arbitrary thing
  • w

    witty-crayon-22786

    11/02/2018, 7:11 PM
    cool. may recommend that as a starter ticket for someone
  • a

    aloof-angle-91616

    11/03/2018, 4:56 AM
    new rule in this channel if someone has a brainblast and figures something out and you see the message you MUST acknowledge it with at least a 🎉 reaction if not more. considering putting "let no success go unacknowledged 🎉" in the topic. just some thoughts
    ❤️ 1
    h
    • 2
    • 1
  • a

    aloof-angle-91616

    11/03/2018, 4:56 AM
    with that said i have yet another project (https://github.com/cosmicexplorer/lex-query) that i thoroughly figured out the build system for in order to procrastinate actually writing and to describe how thoroughly that is i even tried to write a test and the test is failing (and also failing in lint) with an 
    ImportError: No module named pants_test.pants_run_integration_test
    for a test which depends on a 
    pants_requirement()
    in a BUILD file -- this is the file failing: https://github.com/cosmicexplorer/lex-query/blob/master/pants-plugins/upstreamable/tests/test_perl6_run_integration.py. looking in 
    tests/python/pants_test/BUILD
    i see 
    namespace_packages=['pants_test'],
    for the 
    pantsbuild.pants.testinfra
    requirement (and i am adding 
    'pantsbuild.pants.testinfra==%(pants_version)s',
    to pants.ini) -- i have tried various permutations of module import paths but while my python plugin source is working great i can't figure out this import issue. this is on 
    1.11.0rc1
    .
    e
    • 2
    • 5
  • a

    aloof-angle-91616

    11/03/2018, 8:25 AM
    i figured out the above it was because i was assuming too much of 
    pants_requirement()
    -- it covers plugins with the 
    plugins
    entry in pants.ini, but not mere python subpackages such as e.g. 
    pantsbuild.pants.testinfra
    . i ended up making a context-aware object factory to cover pulling in 
    'pantsbuild.pants.testinfra=={}'.format(pants_version())
    into a single 
    python_requirement_library()
    along with pants because that seemed convenient for me
  • m

    mysterious-farmer-45668

    11/05/2018, 6:46 PM
    Getting a unicode error in pants reporting `html_reporter`:
  • m

    mysterious-farmer-45668

    11/05/2018, 6:46 PM
    Copy code
    File "/opt/app-root/src/.cache/pants/setup/bootstrap-Linux-x86_64/1.11.0rc1/lib/python2.7/site-packages/pants/reporting/html_reporter.py", line 320, in handle_output
    f.write(self._htmlify_text(s))

Exception message: 'ascii' codec can't encode character u'\u2713' in position 144: ordinal not in range(128)
  • m

    mysterious-farmer-45668

    11/05/2018, 6:46 PM
    would this be because of a target or something pants internal?
  • m

    mysterious-farmer-45668

    11/05/2018, 6:48 PM
    Actually full stack reveals that this might be a node issue
  • m

    mysterious-farmer-45668

    11/05/2018, 6:49 PM
    could use a clarification:
  • m

    mysterious-farmer-45668

    11/05/2018, 6:49 PM
    -.txt
    -.txt
  • m

    mysterious-farmer-45668

    11/05/2018, 6:49 PM
    stack trace indicates that it originated from 
    node_test
    but the actual exception arises from report
  • m

    mysterious-farmer-45668

    11/05/2018, 6:51 PM
    and 
    \u2713
    seems to be a check mark
  • w

    witty-crayon-22786

    11/05/2018, 7:05 PM
    hm. there is an integration test covering that.
1...208220832084...2420Latest