pantsbuild / pants / 4295

0%

main: 93%

push

travis-ci

Fix ivy_resolve message: Missing expected ivy output file .../.ivy2/pants/internal-...-default.xml

This change forces the exec_ivy() to run if the report is not present.  Sometimes the
targets can all be up to date, but that combination of targets
has not been run through ivy.

This is important because ivy_resolve now depends on
having a valid report from the ivy run to compute the classpath correctly.
The change to use UnionProducts and a more limited compile classpath in https://rbcommons.com/s/twitter/r/1761/
relies on parsing the ivy report.   I added some more error checking in https://rbcommons.com/s/twitter/r/1856/
which started tripping in our build.

Testing Done:
Passed CI @ https://travis-ci.org/pantsbuild/pants/builds/56629304

We got this error message 7 times re-compiling all java_binary() targets in our repo with about 200 targets.
We always run through the targets in alphabetical order: the error starts about 30 minutes into the build after the 80th target.

I created a number of test targets that referenced the same jars in differenc combinations, but was unable to reproduce this outside of our repo.
However, I did put in some debugging before and after exec_ivy() in ivy_resolve
to show what was going on:

```
INFO] Pre exec_ivy() xml report path=/Users/square/.ivy2/pants/internal-<a class=hub.com/pantsbuild/pants/commit/61e19aa02fd5ea667f0e39802a333fa1cd4a74a7">61e19aa02-default.xml exists=False
INFO] All invalidation targets up to date. Skipped execing ivy.
INFO] Post exec_ivy() xml report path=/Users/square/.ivy2/pants/internal-61e19aa02fd5ea667f0e39802a333fa1cd4a74a7-default.xml exists=False
```

Bugs closed: 1350, 1354

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

12919 of 18552 relevant lines covered (69.64%)

0.7 hits per line