On Mon, Dec 12, 2011 at 1:15 PM, Grant Ingersoll <gsing...@apache.org>wrote:
> I'm not sure if it is completely valid, but it seems to me that if our > tests can't run concurrently, it also raises a doubt as to whether some of > our classes can be run concurrently. > I don't think there's a cause for concern; it's really an issue with how the tests proceed, not the code they test. That is, we don't have a problem with stuff returning a wrong answer or failing when tested concurrently, it's that the tests expect something that they probably shouldn't, and that changes with multiple threads. > > I think if we adopt the Lucene test framework (it's a separate JAR), we > can get both the -Dtestseed thing and annotations such as @slow, @nightly, > @weekly, etc. There are probably other useful nuggets in there too. It > should work with Maven. > > All that's needed is a way to (1) run only tests with a certain tag, and then (2) in parallel run in separate JVMs the tests for each tag. If you can figure out (2), you've already got a solution, I imagine: use this to run core/examples/math/integration separately. The slightly nicer thing is that the total runtime of each is probably more balanced than just the slows, just the nightly, etc. No tagging needed.
