Hi Steve, > - tests.threadspercpu seems to behave like a maximum JVM count rather a core > multiplier - is that right? If so, maybe this param should be renamed?
You're right, I don't know how it came to be threadspercpu... it is actually the number of forked JVMs -- it should be "tests.jvms" (sounds good?). There is no reliable way to tell if a cpu is running in hyperthreading mode or with real threads (multicpu motherboards, for example) and from my experiments it seems that going into hyperthreading does not speed up things (possibly because Java has its own concurrent threads anyway so everything's saturated already). I'll rename this attribute -- thanks for spotting this. > - How does "ant -verbose" differ from/replace "ant -Dtests.verbose" ? Are > these complementary? "ant -verbose" is a global switch to run ant's logger in verbose mode. So you'll get tons of logs from tasks other than junit4 runner, but including it. I just reused ant's infrastructure here. -Dtests.verbose is project (lucene/solr) specific. > Would you like me to take a crack at modifying the RunningTests wiki page? Oh, this would be awesome if you could. I am wiki challenged... Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
