I think stage one is pretty much complete - ant test is in a shape that I can do my development work once again at least.
I have many more things planned and some of them need to come before I work much more on eliminating all Jenkins fail emails. So, while I'll still work on fixing fails off and on in the short term, for a bit it will be much less of a focus. In the near future and once some other things are in place, I'll start pushing on phase 2. In the meantime, there are only a handful of issues left in comparison to what we started with - I encourage everyone to help tackle fails as they show up from Jenkins in your inbox and to beast new tests before you commit them, and to beast tests you change, and to run the tests many times when making large or invasive changes. You can beast a test with something like this (from the module the test belongs to): ant clean beast -Dtests.jvms.override=6 -Dbeast.iters=60 -Dtests.dups=6 -Dtests.iters=5 -Dtestcase=DocValuesNotIndexedTest This runs 6 tests at a time in parallel - the largest limitation on raising this is that each one needs around 500-600MB of RAM. I often use 12-24 jvms with lots of RAM or SWAP. It's important to bog down your hardware to mimic the various environments tests must still pass in. -- - Mark http://about.me/markrmiller
