Thanks Rupert for your response.

I don't see any issues with the permissions. Everything is accessable by my
local user. I also have rerun the build with:

    sudo MAVEN_OPTS="-Xmx2048M -XX:MaxPermSize=512M" mvn clean install -e

But that didn't work either.

I also tried to increase the memory for the test runs by following this
stackoverflow answer: http://stackoverflow.com/a/12415230/199848
Therefore I added the following snippet to the file
/vagrant/stanbol/entityhub/indexing/source/jenatdb/pom.xml

    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-surefire-plugin</artifactId>
      <configuration>
        <forkMode>pertest</forkMode>
        <argLine>-Xms512m -Xmx1024m</argLine>
        <testFailureIgnore>false</testFailureIgnore>
        <skip>false</skip>
        <includes>
          <include>**/*.java</include>
        </includes>
      </configuration>
    </plugin>

I have now setup a completely new virtualmachine so none of my earlier tries
interferes. But I have the same problem.

Here is the information that will hopefully help in finding the related
issue:

    
vagrant@precise64:/vagrant/stanbol/entityhub/indexing/source/jenatdb/target/test-files/testConfigs/iterable/indexing/resources/tdb#
ls -lah
    total 8.1M
    drwxrwxr-x 1 vagrant vagrant 4.0K Nov 14 12:23 .
    drwxrwxr-x 1 vagrant vagrant 4.0K Nov 14 12:23 ..
    -rw-r--r-- 1 vagrant vagrant 8.0M Nov 14 12:23 node2id.dat
    -rw-r--r-- 1 vagrant vagrant    0 Nov 14 12:23 node2id.idn

You can find the listed files here to download:

    https://www.dropbox.com/sh/jfb5csufonxv2g8/-y49f7gN-x


Thanks so much!
Gregor

2013/11/14 Rupert Westenthaler <rupert.westentha...@gmail.com>

> Hi Gregor,
>
> The test encounters an IOException when allocating a segment in a
> memory mapped file (see  [1] line 221) used by Jena TDB. Based on the
> stack trace this happen already during the initialization of the Jena
> TDB store. So I my guess would be that either one of the memory mapped
> file used by Jena is corrupted or missing read/write permission on the
> file.
>
> The first can only be the case if there would still be data from a
> previous run of the test. Actually this test does has a known issue
> that it does not delete files from previous runs. Including the
> "clean" prevents this as this ensures that the /target folder is
> deleted before running the tests.
>
> To check permissions: the Jena TDB store created by the tests are located
> under
>
>
> {module-home}/target/test-files/testConfigs/{test-config-name}/indexing/resources/tdb
>
> e.g.
>
>
> /vagrant/stanbol/entityhub/indexing/source/jenatdb/target/test-files/testConfigs/iterable/indexing/resources/tdb
>
> for the failed testEntityDataIterable test.
>
> If both does not solve the issue I would suggest to provide the Jena
> TDB store (all files in the tdb folder) to make some further tests.
>
> best
> Rupert
>
>
>
> [1]
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.jena/jena-tdb/0.10.0/com/hp/hpl/jena/tdb/base/file/BlockAccessMapped.java
>

Reply via email to