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

    jolly-chef-92794

    03/30/2016, 2:20 PM
    @melodic-kite-14017: It looks the the jar builder is mistaking a 
    pom
    file for a jar file
  • j

    jolly-chef-92794

    03/30/2016, 2:21 PM
    Maybe it has the wrong classifier/type in a dependency somewhere?
  • j

    jolly-chef-92794

    03/30/2016, 2:21 PM
    If you aren’t depending on it directly it may be a transitive dependency (one of of the external artifacts you depend on may in turn depend on it; maybe one of your dependencies has a malformatted pom file?)
  • m

    melodic-kite-14017

    03/30/2016, 2:22 PM
    If depmap doesn't contain curator, is there another good way to find out where it is coming from?
  • b

    bored-art-40741

    03/30/2016, 2:23 PM
    As a first check, can you 
    ls -hal
    that directory/file and see where it's symlinking to? And then see if that file is somehow malformed?
  • a

    ancient-stone-50795

    03/30/2016, 2:24 PM
    @melodic-kite-14017: This error you are getting comes from running the 'jar-tool' java executable.
  • j

    jolly-chef-92794

    03/30/2016, 2:24 PM
    You can peek at the 
    compile_classpath
    folder under 
    .pants.d/compile/zinc/<sha>/<target id>/current/classes/compile_classpath/
    for each target to see what classpath each jvm target you’re building is, which can narrow down which dependencies may be the issue
  • a

    ancient-stone-50795

    03/30/2016, 2:24 PM
    You can see its command line by adding 
    -ldebug
    I think you will find that you have a dependency on a dep that is a 
    pom
    packaged file.
  • a

    ancient-stone-50795

    03/30/2016, 2:25 PM
    Ideally, we would just ignore this kind of dep or bundle it in as a specific file, but it looks like its being passed as if it is a jar to bundle in.
  • j

    jolly-chef-92794

    03/30/2016, 2:25 PM
    If you don’t think it’s necessary you could try 
    deploy_exclude
    -ing it
  • a

    ancient-stone-50795

    03/30/2016, 2:25 PM
    Garrett and I are talking about the same issue but different ways to debug it.
  • j

    jolly-chef-92794

    03/30/2016, 2:25 PM
    from the jvm binary
  • a

    ancient-stone-50795

    03/30/2016, 2:26 PM
    And conveniently interleaving our suggestions.
  • j

    jolly-chef-92794

    03/30/2016, 2:26 PM
    Yeah slack is helpful like that
  • m

    melodic-kite-14017

    03/30/2016, 2:26 PM
    ha. let me read through these and try a few of the options. I already tried ldebug and I can see a pom being pulled in right inline with jars:
    Copy code
    dumping org.apache.ant:ant:1.9.1::jar from /.pants.d/ivy/jars/org.apache.ant/ant/jars/ant-1.9.1.jar
dumping org.apache.ant:ant-launcher:1.9.1::jar from /.pants.d/ivy/jars/org.apache.ant/ant-launcher/jars/ant-launcher-1.9.1.jar
dumping org.apache.curator:apache-curator:2.6.0::pom from /.pants.d/ivy/jars/org.apache.curator/apache-curator/poms/apache-curator-2.6.0.pom
dumping org.codehaus.groovy:groovy-all:2.1.6::jar from /.pants.d/ivy/jars/org.codehaus.groovy/groovy-all/jars/groovy-all-2.1.6.jar
dumping org.iq80.snappy:snappy:0.2::jar from /.pants.d/ivy/jars/org.iq80.snappy/snappy/jars/snappy-0.2.jar
  • j

    jolly-chef-92794

    03/30/2016, 2:27 PM
    Yeah it looks like pants thinks 
    apache-curator-2.6.0.pom
    is a jar
  • j

    jolly-chef-92794

    03/30/2016, 2:27 PM
    Which is fine for compile/run/test because it’ll just be added to the classpath
  • j

    jolly-chef-92794

    03/30/2016, 2:27 PM
    But 
    binary
    will try to unzip it to bundle its contents into your fatjar
  • a

    ancient-stone-50795

    03/30/2016, 2:30 PM
    @melodic-kite-14017: if you can provide a small repro case I think we can handle this for most cases. Pants can tell the difference between different 
    type
    of external deps. The default is 
    jar
    but this one should be marked as 
    pom
  • m

    melodic-kite-14017

    03/30/2016, 2:32 PM
    I'll try to do that. Thanks for all the help!
  • m

    melodic-kite-14017

    03/30/2016, 2:40 PM
    quick update -- using deploy_excludes helps. it at least gets past that step, then runs into 
    java.lang.OutOfMemoryError: GC overhead limit exceeded
    in the jar builder
  • b

    bored-art-40741

    03/30/2016, 2:42 PM
    @melodic-kite-14017: Common issue
  • b

    bored-art-40741

    03/30/2016, 2:42 PM
    We have this in our pants.ini
  • b

    bored-art-40741

    03/30/2016, 2:42 PM
    Copy code
    [jar-tool]
jvm_options: ['-Xms2g','-Xmx2g', '-Djava.io.tmpdir=%(pants_workdir)s']
  • b

    bored-art-40741

    03/30/2016, 2:42 PM
    The tmpdir stuff is optional and specific to something weird in our environment
  • m

    melodic-kite-14017

    03/30/2016, 2:43 PM
    cool. thanks
  • a

    adorable-glass-89507

    03/30/2016, 2:44 PM
    it looks like pants uses a single env for python, even if a single invocation of 
    ./pants binary
    includes multiple 
    python_binary
    targets -- is there some way around it, have pants create a chroot per python_binary target? It even seems to mix the actual runner env with what is currently being built, at least when running tests, I also wonder if there's some way to create separation between those as well.
  • b

    bored-art-40741

    03/30/2016, 2:47 PM
    That should not be the case, as far as I understand it
  • b

    bored-art-40741

    03/30/2016, 2:47 PM
    Pants should generate one chroot (potentially cached) per target
  • b

    bored-art-40741

    03/30/2016, 2:48 PM
    I believe @happy-kitchen-89482 is the expert on that code
1...110711081109...2420Latest