The order is undefined in java itself: its randomish in sun's java 7 for instance (and maybe other implementations, too). We just made it random always, so it will fail consistently regardless of JRE implementation.
Adding CHANGES.txt to test changes seems like a slippery slope, the behavior and APIs here is undefined, we can and should break it at any time we want without any hesitation or notice, and it should be assumed that all things are random :) On Sun, Jul 24, 2011 at 3:21 PM, Chris Hostetter <[email protected]> wrote: > > : i don't think thats very important, its just our internal tests, and > everyone here is a committer. > > Wasn't the new randomization added to the "test-framework" ? > > we advertise that as a package users can use to write their own tests > using lucene -- if we had tests that depended on order other people using > the framework could as well, seems important to tell them when > upgrading... > > "Tests using the test-framework that passed using previous versions may > now fail if the had an implicit dependency on test ordering" > > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
