Splendid work Mark! I do have one question, what't the relationship between the "beast" target and "the best damn beasting script in the world (tm)"? When would you prefer one over the other?
All: And I'm assuming that the priority going forward be fixing Jenkins tests that are failing first, and unravelling tests annotated with AwaitsFix second. If we let Jenkins fails build up again we'll shortly be back in the same situation we are now. I'm going to let this settle a little, last time I checked there were 80 or so tests that are BadApple'd that haven't failed in the last 4 test rollups I pulled from Hoss' reports. I'll un-badapple them sometime over the holidays. I want the changes made lately to have a chance to work through the system, it takes about a month for things to settle out enough to have a track record to work from. Erick Erick On Sun, Dec 16, 2018 at 8:36 AM Mark Miller <[email protected]> wrote: > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
