On Wed, Dec 5, 2012 at 2:23 PM, Uwe Schindler <[email protected]> wrote:
> The security manager only prevents writing of files outside the build > directory, but it cannot restrict the JVMs to only write into their own > working directory…. We could try this at some time, but then also the > JUnit4 CarrotSearch stuff must respect this. So if all tests running in > parallel share the same config directory, then can drive crazy. So the > timestamp file should be **private** to the test, so the tests should > store them in their working directory (as reported by the temporary > directory functions in LuceneTestCase).**** > > ** ** > > The issue only happens on Policeman server in Linux, but not in Windows, > because Windows VM only uses one JVM to run tests, while Linux uses 2 > parallel JVMS… The FreeBSD one is also running with 2 JVMs, but this server > runs the test much more seldom because it has a lot of other stuff to do…* > *** > > ** ** > > James: How many JVMs does your machine use (you see this at the beginning > when tests start to run)?**** > > ** ** > > ok this is the bug. See dih's build.xml: <!-- the tests have some parallel problems: writability to single copy of dataimport.properties --> <property name="tests.jvms" value="1"/> The problem is: policeman jenkins server overrides this by setting the -D !!!!!!!!
