bq. In my opinion, the better way would be to “lock” the whole checkout and prevent parallel ANT runs.
I share Uwe's viewpoint here. bq. The java.io.tmpdir sysprop is only set by the ANT build from the ANT script, the junit4 task does not modify the property at all – as Eclipse does not run the ant script, you have to configure java.io.tempdir yourself. We could probably set this property somewhere very early in LuceneTestCase's filter chain. But this would then limit the flexibility of tuning things from the outside (from ant, etc.). Don't know if it's a good idea. Anyway, Shai, if it's your own checkout (or project) and you absolutely have to have parallel tests running on the same structure (I assume only tests will fork, nothing else) then you could set up a random cwd for subprocesses from ant -- http://ant.apache.org/manual/Tasks/tempfile.html generate a temporary directory in place of that property and reuse it for 'dir' attribute of junit4. This shouldn't clash with other JVMs (but who knows). Note that the J0/J1 and other working directories are specified using 'dir' attribute of junit4 task: http://labs.carrotsearch.com/download/randomizedtesting/2.0.0/docs/junit4-ant/Tasks/junit4.html The 'isolateWorkingDirectories' attribute was added specifically to avoid multiple JVMs conflicts but it is still assumed that the 'dir' attribute is unique to the current build and isolated from any other process. The tempdir, on the other hand, can be pointed to any folder, regardless of the number of concurrent processes because files in there will not conflict with each other (they are timestamp prefixed). Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
