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

LAST BUILD BRANCH: tdyas/reapi/another-regression-test
DEFAULT BRANCH: main
Ran
Files 325
Run time 17s
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
coverage: 65.795% (+0.08%) from 65.717%
CI_FLAGS="-fkmsrcn -u 1/2 'Unit tests for pants and pants-plugins - shard 2'"

push

travis-ci

baroquebobcat 
Apply excludes consistently across classpaths

We ran into an issue with isolated compile and excludes.

1. compiling a target that excludes a jar that its dependency requires with the isolated strategy without build cache enabled will cause that dependency to fail to compile, because the ivy resolve excludes the jar entirely.
2. If you use the `resolve.ivy --soft-excludes` option, then the jar will be resolved. But, it will no longer be excluded from the classpath of the target that excludes it. This can cause runtime issues because the excluded jars may end up on the classpath together with the jars that replace them.

What this change does is
- move classpath manipulations into static helper methods
- filter classpaths for excluded jars after they are constructed everywhere they are constructed

The exclude strategy I've ended up at is to collect all the transitive excludes, convert them into partial file paths, and strip jars that match. This has a behavior that's similar to how the global strategy works.

Testing Done:
I ran a test suite that runs into the issues with log4j and log4j-over-slf4j with the changes and saw that tests ran successfully rather than failing to compile or blowing the stack.

I'm also working on a unit test suite and an integration suite.

Bugs closed: 1562

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

12830 of 19500 relevant lines covered (65.79%)

0.66 hits per line

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