OK - I'm pretty sure I won't hit my 5pm MST deadline for pants release with travis ci queues like they are so I'll get out the CHANGELOG+version bump nowish and edit the CHANGELOG as needed later tonight

Oh I did have to xfail the eight test

Given the nature of the error, I think there's a real issue with the test there

It seems like it's using the wrong JDK version

Out of curiosity @enough-analyst-54434 what is the default JDK on your system?

If it's 8, can you change it to 7 and rerun that eight test?

Yup:

$ JAVA_HOME=/usr/lib/jvm/java-7-openjdk ./pants test tests/python/pants_test/backend/jvm/tasks:junit_run_integration -- -v
...
                    tests/python/pants_test/backend/jvm/tasks/test_junit_run_integration.py::JunitRunIntegrationTest::test_java_eight FAILED
                     tests/python/pants_test/backend/jvm/tasks/test_junit_run_integration.py::JunitRunIntegrationTest::test_java_seven PASSED
...

So test is bad

Okay good to know

I'm going to mark it xfail and open an issue

sgtm

Not sure I've ever seen a green Jenkins integration run

funny that i just realized that jenkins execution space can be pretty dirty as well

git clean -fdx
+ git clean -fdx
Skipping repository .cache/pants
Removing .cache/bootstrap
Removing .cache/intellij
Removing .cache/jdk-libs
Removing .ivy2/
Removing .pants.d/
Removing .pids/
Removing 1/
Removing a.sh
Removing light_idea_test_case.iml
Removing run.sh

everything outside of .cache, .ivy2, .pants.d and .pids should likely turn into bugs against unit tests or whatever is generating these loose files.

=kwlzn

D:

Seems like maven is now unhappy with how frequently we're hitting it in our isolated tests

Super sigh, it would be nice to have a read-through cache for this

Jenkins build finished: https://github.com/pantsbuild/pants/pull/2895

One failure, timeout to maven

Travis is still queueing

A read through cache, from what I've seen, would be an S3 curl and tar explode at the beginning of the CI command and adding a tarball step to the end of the (successful) CI command and then send that to S3. Not sure if that can work with 4sq budget for this, but I'm willing to pay for the bucket and assign keys

I think I need to be more willing to pay for a lawyer soon though and form an org

i might know one.

I'll add an apropos anecdote at this juncture: I'll be an Apache Thrift committer in the next month fwict and that Apache project is poor because .... too little process

They accept patches too easily

hah

So I am absolutley not seeing the apache too stodgy argument in the 2 projects I'm actively involved in