On 12/03/15 11:38, Claude Warren wrote:
First let me start with a disclaimer: I do not run windows, I have not
attempted to run the windows TDB tests, I have only followed the
conversation tangentially.
My understanding of the testing issue is that Windows does not release the
disk space associated with memory mapped files until after the JVM exits.
Q: Is it not possible to add a configuration option to Maven that causes
those tests to be run in a different JVM. When the test finishes the JVM
should clean up the files. Not sure if that makes sense but a discussion
of how to configure Maven to do the new JVM per test is found here:
http://stackoverflow.com/questions/6813373/how-to-tell-maven2-to-execute-junit-tests-one-by-one-each-in-new-jvm-instance
Claude
Jena_Development_Test_Windows runs again now - it has the maven test
step set to use "-Pdev" so it includes TDB but not jdbc-tdb. (IIRC the
JDBC tests use more space than the TDB ones).
Andy
-------- Forwarded Message --------
Subject: Jenkins build is back to normal : Jena_Development_Test_Windows
#518
Date: Thu, 12 Mar 2015 12:32:50 +0000 (UTC)
From: Apache Jenkins Server <[email protected]>
Reply-To: [email protected]
To: [email protected]
See <https://builds.apache.org/job/Jena_Development_Test_Windows/518/>
-------- Forwarded Message --------
