• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

pantsbuild / pants / 6799 / 3
0%
main: 93%

Build:
Build:
LAST BUILD BRANCH: 2.32.x
DEFAULT BRANCH: main
Ran 11 Sep 2015 03:50PM UTC
Files 388
Run time 34s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Sep 2015 03:43PM UTC coverage: 71.537% (-0.001%) from 71.538%
CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'"

push

travis-ci

gmalmquist
Make BootstrapJvmTools fail fast on a bad user-specified address.

Previously, if you specified a target for a jvm-tool that pants
failed to resolve, if the jvm-tool had a default classpath, pants
would simply inject a synthetic JarLibrary with the same name that
used the default classpath.

This resulted in pants pretending to use the user-specified target
that it couldn't find, but silently it was using the default.

This caused problems for square internally when we tried to specify
a different version of the wire-compiler with an (unwittingly)
malformatted spec. The build continued along merrily and subtly
pulled in the wrong version of wire, only blowing up when it tried
to compile a target that used features not available in pants's
default version of wire.

Example output after this change:

    ~/Src/Pants ./pants --gen-wire-wire-compiler="this-target-definitely-does-not-exist" clean-all compile examples/src/wire::
    INFO] Detected git repository at /Users/gmalmquist/Src/Pants on branch gmalmquist/missing-jvm-tool-options-fail-loudly

    17:41:55 00:00 [main]
                   (To run a reporting server: ./pants server)
    17:41:55 00:00   [bootstrap]
    17:41:55 00:00   [setup]
    17:41:55 00:00     [parse]
    FAILURE: Failed to resolve target for tool: this-target-definitely-does-not-exist. This target was obtained from
    option wire-compiler in scope gen.wire.

    Make sure you didn't make a typo in the tool's address. You specified that the
    tool should use the target found at "this-target-definitely-does-not-exist".

    This target has a default classpath configured, so you can simply remove:
      [gen.wire]
      wire-compiler: this-target-definitely-does-not-exist
    from pants.ini (or any other config file) to use the default tool.

    The default classpath is: com.squareup.wire-wire-compiler-1.6.0

    Note that tool target addresses in pants.ini should be specified *without* quotes.

    17:41:55 00:00   [complete]
                   FAILURE

Testing Done:
Manual testing, added tests to test_bootstrap_jvm_tools_integration.

CI went green here: https://travis-ci.org/gmalmquist/pants/builds/79863183
CI went green here: https://travis-ci.org/gmalmquist/pants/builds/79869416

Bugs closed: 2167

Reviewed at https://rbcommons.com/s/twitter/r/2795/

16741 of 23402 relevant lines covered (71.54%)

0.72 hits per line

Source Files on job 6799.3 (CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'")
  • Tree
  • List 0
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 6799
  • Travis Job 6799.3
  • 4d5904d2 on github
  • Prev Job for CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'" on master (#6790.3)
  • Next Job for CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'" on master (#6800.3)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc