[
https://issues.apache.org/jira/browse/JENA-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364437#comment-15364437
]
Andy Seaborne commented on JENA-1189:
-------------------------------------
Sounds reasonable to me though I don't know the code that well. It does seem
better to have a reliable build on OSX.
A very small number (1 is a very small number!), disk-based tests to check that
file names work would be useful.
TDB does support named memory locations (see {{Location}}) or a unique each
time one.
> Resolve problems with jena-jdbc-driver-tdb tests on Macs
> --------------------------------------------------------
>
> Key: JENA-1189
> URL: https://issues.apache.org/jira/browse/JENA-1189
> Project: Apache Jena
> Issue Type: Bug
> Components: JDBC
> Affects Versions: Jena 3.1.0
> Reporter: A. Soroka
> Assignee: A. Soroka
> Priority: Minor
> Labels: jdbc
>
> Two tests in jena-jdbc-driver-tdb (TestTdbDiskResultSets and
> TestTdbDiskConnection) create a lot of temporary data while running, in the
> form of on-disk TDB datasets. If those datasets don't get deleted promptly as
> they are not longer needed, they can fill up the disk and blow out the build.
> This seems to be happening both on Windows and Mac boxes. In the Windows
> case, there is a known problem with Java being unable to release files once
> they have been memory-mapped. But for Macs, it should be possible to smarten
> up the test framework a bit to ensure that filesystem resources are getting
> released promptly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
