3
0%
main: 93%

Ran 15 Sep 2015 10:10PM UTC

Files 392

Run time 103min

Badge

Embed ▾

Committed 15 Sep 2015 09:46PM UTC coverage: 70.966% (-0.1%) from 71.064%

Job # CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'"

Build Type

push

travis-ci

Committed by

gmalmquist

Commit Message

Adding a console task to explain where options came from.

Since pants allows options in config files that haven't been
registered, it's easy to accidentally typo an option and have
pants silently ignore your config.

It can also be tricky to know what options end up getting used when
you might have flags set via multiple config files, through env
variables, and by flags set in wrapper scripts.

This makes it easy to verify if options you set in pants.ini or
elsewhere are actually sticking/not getting overriden by something
else.

It might also be cool to plumb this information through to the
pants server UI at some point.

Testing Done:
Added tests to tests/python/pants_test/option/test_options_integration.py and tests/python/pants_test/option/test_options.py.

CI went green here: https://travis-ci.org/gmalmquist/pants/builds/80306892
CI went green here: https://travis-ci.org/gmalmquist/pants/builds/80484138
CI went green here: https://travis-ci.org/pantsbuild/pants/builds/80508164

Bugs closed: 2192

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

Run Details

16787 of 23655 relevant lines covered (70.97%)

0.71 hits per line

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

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6873.3 (CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'")

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

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6873.3 (CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'")

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

README BADGES
x