So my Gradle landing might be a little delayed, I've burned myself out a little trying to get Solr tests to perform at top speed due to Gradle's "dumb" parallel test distribution.
I extended the Gradle test task and made my own testFast target that is "smart" and has been fun to play with, but that only drew me back into the test quagmire I've been in and out of before. As soon as I saw tests start to move faster, I was hooked again. The worst kind of addiction, every additional diminishing savings costing more blood. In the end I fixed a bunch more bs, pulled in a bunch of improvements and fixes around tests from the Starburst branch that had not come over yet, and have generally been wrapping my magic lasso around this test suite. A bunch of that includes stuff in the code that was causing test problems or slowness. I've put a lot of emphasis on moving actual slow stuff to @Nightly runs and fixing not actual slow stuff. On my 18 core dev machine, I've gotten down to about 7 minutes for all the Solr modules currently in the Gradle build (there might be a new one not there). There is a bunch of clean up I have to do, and review of some things, and again it's a rather large ''patch". I'd like to get it out of my gradle branch and into master before moving in Gradle, so I plan to put up a PR when I can in the near future and am hoping for some help with review. Thanks, -- - Mark http://about.me/markrmiller
