You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Gregor Müllegger <gr...@muellegger.de> on 2013/11/13 22:37:37 UTC
Building stanbol fails with tests for org.apache.stanbol.entityhub.indexing.source.jenatdb
Hi,
I just want to get started with Apache Stanbol but experience issues during
my
build. I get the following output:
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 26:30.064s
[INFO] Finished at: Wed Nov 13 21:11:28 UTC 2013
[INFO] Final Memory: 118M/390M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on
project org.apache.stanbol.entityhub.indexing.source.jenatdb: There are
test failures.
[ERROR]
[ERROR] Please refer to
/vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports
for the individual test results.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test
(default-test) on project
org.apache.stanbol.entityhub.indexing.source.jenatdb: There are test
failures.
Please refer to
/vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports
for the individual test results.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test
failures.
Please refer to
/vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports
for the individual test results.
at
org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:87)
at
org.apache.maven.plugin.surefire.SurefirePlugin.writeSummary(SurefirePlugin.java:651)
at
org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:625)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:136)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:97)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with
the command
[ERROR] mvn <goals> -rf
:org.apache.stanbol.entityhub.indexing.source.jenatdb
This seems interesting as well in the output, a bit above:
Tests in error:
testEntityDataIterable(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
BlockMgrMapped.segmentAllocate: Segment = 0
testEntityDataProvider(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
BlockMgrMapped.segmentAllocate: Segment = 0
testQuadsImport(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
BlockMgrMapped.segmentAllocate: Segment = 0
testBNodeSupport(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
BlockMgrMapped.segmentAllocate: Segment = 0
Tests run: 10, Failures: 0, Errors: 4, Skipped: 0
And here ist the content of the
/vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports/org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest.txt
file:
http://pastebin.com/Zv4gU7Gi
Unfortunatelly I don't have any idea why this might be failing :-/
I'm using r1541504, Maven 3.0.4, Ubuntu 12.04 64bit,
"openjdk-7-jdk" 7u25-2.3.10-1ubuntu0.12.04.2 from ubuntu repositories.
I also used the `export MAVEN_OPTS="-Xmx1024M -XX:MaxPermSize=256M"` as
explained in the docs before trying to build with `mvn install`
Does anyone of you might know more about this?
I'm ofcourse happy to provide more information if necessary.
Thanks already in advance,
Gregor
Re: Building stanbol fails with tests for org.apache.stanbol.entityhub.indexing.source.jenatdb
Posted by Gregor Müllegger <gr...@muellegger.de>.
Hi,
I have new results. Your comment about permissions got me thinking. I was
running the build in a VirtualBox machine, and the build was located in a
shared directory (which is essentially a directory on the host, that gets
mounted inside the virtual machine). Maybe this caused the access to the
files
beeing different than beeing expected on a local filesystem.
I checked out the repo in another directory (which is not a shared
directory,
but a normal one on the root filesystem). And rebuild. The error about
jenatdb went away! So thanks for your help!
However a new one arises:
Failed tests:
testSparqlConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest):
GET request to
http://localhost:8765/enhancer/sparql?query=PREFIX+enhancer%3A+%3Chttp%3A%2F%2Fstanbol.apache.org%2Fontology%2Fenhancer%2Fenhancer%23%3EPREFIX+rdfs%3A+++++%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23%3ESELECT+distinct+%3Fname+%3Fchain+WHERE+%7B%3Fchain+a+enhancer%3AEnhancementChain+.%3Fchain+rdfs%3Alabel+%3Fname+.%7DORDER+BY+ASC%28%3Fname%29:
expecting status 200 (content: <html>(..)
testEngineConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest):
GET request to http://localhost:8765/enhancer/engine: no match for regexp
'<j.0:hasEngine
rdf:resource="http://localhost:.*/enhancer/engine/dbpediaLinking"/>',
content=(..)
Tests run: 180, Failures: 2, Errors: 0, Skipped: 0
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Stanbol Releasing Source Assembly Descriptor SUCCESS
[3.342s]
... output shortened ...
[INFO] Apache Stanbol Enhancer Engine Archetype .......... SUCCESS
[0.378s]
[INFO] Apache Stanbol Integration Tests .................. FAILURE
[8:23.365s]
[INFO] Apache Stanbol Reactor NG ......................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 33:25.063s
[INFO] Finished at: Thu Nov 14 13:22:55 UTC 2013
[INFO] Final Memory: 594M/1306M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on
project org.apache.stanbol.integration-tests: There are test failures.
[ERROR]
[ERROR] Please refer to
/home/vagrant/stanbol/integration-tests/target/surefire-reports for the
individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with
the command
[ERROR] mvn <goals> -rf :org.apache.stanbol.integration-tests
And here is the traceback:
vagrant@precise64:~/stanbol/integration-tests/target/surefire-reports$
cat
/home/vagrant/stanbol/integration-tests/target/surefire-reports/org.apache.stanbol.enhancer.it.EnhancerConfigurationTest.txt
-------------------------------------------------------------------------------
Test set: org.apache.stanbol.enhancer.it.EnhancerConfigurationTest
-------------------------------------------------------------------------------
Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.664
sec <<< FAILURE!
testSparqlConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest)
Time elapsed: 0.577 sec <<< FAILURE!
java.lang.AssertionError: GET request to
http://localhost:8765/enhancer/sparql?query=PREFIX+enhancer%3A+%3Chttp%3A%2F%2Fstanbol.apache.org%2Fontology%2Fenhancer%2Fenhancer%23%3EPREFIX+rdfs%3A+++++%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23%3ESELECT+distinct+%3Fname+%3Fchain+WHERE+%7B%3Fchain+a+enhancer%3AEnhancementChain+.%3Fchain+rdfs%3Alabel+%3Fname+.%7DORDER+BY+ASC%28%3Fname%29:
expecting status 200 (content: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 Server Error</title>
</head>
<body>
<h2>HTTP ERROR: 500</h2>
<p>Problem accessing /enhancer/sparql. Reason:
<pre> Server Error</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>
) expected:<200> but was:<500>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at
org.apache.stanbol.commons.testing.http.RequestExecutor.assertStatus(RequestExecutor.java:175)
at
org.apache.stanbol.enhancer.it.EnhancerConfigurationTest.testSparqlConfig(EnhancerConfigurationTest.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
testEngineConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest)
Time elapsed: 0.376 sec <<< FAILURE!
java.lang.AssertionError: GET request to
http://localhost:8765/enhancer/engine: no match for regexp '<j.0:hasEngine
rdf:resource="http://localhost:.*/enhancer/engine/dbpediaLinking"/>',
content=
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:j.0="http://stanbol.apache.org/ontology/enhancer/enhancer#" >
<rdf:Description rdf:about="http://localhost:8765/enhancer">
<rdf:type rdf:resource="
http://stanbol.apache.org/ontology/enhancer/enhancer#Enhancer"/>
</rdf:Description>
</rdf:RDF>
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.stanbol.commons.testing.http.RequestExecutor.assertContentRegexp(RequestExecutor.java:266)
at
org.apache.stanbol.commons.testing.http.RequestExecutor.assertContentRegexp(RequestExecutor.java:240)
at
org.apache.stanbol.enhancer.it.EnhancerConfigurationTest.testEngineConfig(EnhancerConfigurationTest.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
I have also tried again after half an hour waiting, based on the information
in this mail [1] - since it suggests that the integration tests might fail
from
time to time. But it still fails with the same error.
Thanks again! At least we found the reason for the jenatdb issue!
Gregor
[1] http://mail-archives.apache.org/mod_mbox/stanbol-dev/201211.mbox/
<CA...@mail.gmail.com>
2013/11/14 Rupert Westenthaler <ru...@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
>
Re: Building stanbol fails with tests for org.apache.stanbol.entityhub.indexing.source.jenatdb
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Gregor,
I was seeing your mail but only after I sent my response as I was
working offline in the train an my way from home to work.
In the trunk it is expected that two integration tests do fail. This
is because the SPARQL serializer/deserializer are not yet ported to
the new framework used in the trunk. If you are not planing to use the
SPARQL endpoint of Stanbol this should not affect you.
best
Rupert
On Wed, Nov 20, 2013 at 12:33 PM, Gregor Müllegger <gr...@muellegger.de> wrote:
> Hi and thanks again for beeing so persistent in helping me.
>
> I think the TDB issue went away after I relocated the stanbol checkout to a
> local directory. The tdb directory now contains all the files that you have
> listed. The successfull test results of your special testcase can be found
> here: http://pastebin.com/FAJKJpGT
>
> However I've already written a new response that might have slipped through
> your inbox. It can be viewed here in total:
> http://mail-archives.apache.org/mod_mbox/stanbol-dev/201311.mbox/<
> CALjSGCPkviFfR7PL_460NrsBjjT-cpdUaAdf4P1FEwsxqoOkzw@mail.gmail.com>
>
> The integration tests are failing with the message:
>
> Failed tests:
> testSparqlConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest):
> GET request to
> http://localhost:8765/enhancer/sparql?query=PREFIX+enhancer%3A+%3Chttp%3A%2F%2Fstanbol.apache.org%2Fontology%2Fenhancer%2Fenhancer%23%3EPREFIX+rdfs%3A+++++%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23%3ESELECT+distinct+%3Fname+%3Fchain+WHERE+%7B%3Fchain+a+enhancer%3AEnhancementChain+.%3Fchain+rdfs%3Alabel+%3Fname+.%7DORDER+BY+ASC%28%3Fname%29:
> expecting status 200 (content: <html>(..)
>
> testEngineConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest):
> GET request to http://localhost:8765/enhancer/engine: no match for regexp
> '<j.0:hasEngine
> rdf:resource="http://localhost:.*/enhancer/engine/dbpediaLinking"/>',
> content=(..)
>
>
> Best regards,
> Gregor
>
>
> 2013/11/15 Rupert Westenthaler <ru...@gmail.com>
>
>> Hi Gregor,
>>
>> The folder is expected to include the following files
>>
>> GOSP.dat GPOS.idn OSP.dat OSPG.idn POSG.dat SPO.idn node2id.dat
>> prefix2id.dat prefixIdx.idn
>> GOSP.idn GSPO.dat OSP.idn POS.dat POSG.idn SPOG.dat node2id.idn
>> prefix2id.idn prefixes.dat
>> GPOS.dat GSPO.idn OSPG.dat POS.idn SPO.dat SPOG.idn nodes.dat
>> prefixIdx.dat stats.opt
>>
>> As you are missing those files it indicates that the initialization of
>> the TDB store is failing.
>>
>> IMO this looks like an issue with Jena TDB specific to your
>> environment. To validate this I have creates a minimal test module [1]
>> that (1) create a Jena TDB store, (2) adds an quad and (3) a Triple to
>> the default Graph. If this also fails in your Environment the logs
>> should be useful to file a Bug with Jena TDB.
>>
>> To execute the test just extract the archive and call "mvn test" in
>> the module directory.
>>
>> best
>> Rupert
>>
>> [1] http://dev.iks-project.eu/downloads/stanbol-launchers/tdbtest.tar.bz2
>>
>>
>>
>> On Thu, Nov 14, 2013 at 1:48 PM, Gregor Müllegger <gr...@muellegger.de>
>> wrote:
>> > 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 <ru...@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
>> >>
>>
>>
>>
>> --
>> | Rupert Westenthaler rupert.westenthaler@gmail.com
>> | Bodenlehenstraße 11 ++43-699-11108907
>> | A-5500 Bischofshofen
>>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: Building stanbol fails with tests for org.apache.stanbol.entityhub.indexing.source.jenatdb
Posted by Gregor Müllegger <gr...@muellegger.de>.
Hi and thanks again for beeing so persistent in helping me.
I think the TDB issue went away after I relocated the stanbol checkout to a
local directory. The tdb directory now contains all the files that you have
listed. The successfull test results of your special testcase can be found
here: http://pastebin.com/FAJKJpGT
However I've already written a new response that might have slipped through
your inbox. It can be viewed here in total:
http://mail-archives.apache.org/mod_mbox/stanbol-dev/201311.mbox/<
CALjSGCPkviFfR7PL_460NrsBjjT-cpdUaAdf4P1FEwsxqoOkzw@mail.gmail.com>
The integration tests are failing with the message:
Failed tests:
testSparqlConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest):
GET request to
http://localhost:8765/enhancer/sparql?query=PREFIX+enhancer%3A+%3Chttp%3A%2F%2Fstanbol.apache.org%2Fontology%2Fenhancer%2Fenhancer%23%3EPREFIX+rdfs%3A+++++%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23%3ESELECT+distinct+%3Fname+%3Fchain+WHERE+%7B%3Fchain+a+enhancer%3AEnhancementChain+.%3Fchain+rdfs%3Alabel+%3Fname+.%7DORDER+BY+ASC%28%3Fname%29:
expecting status 200 (content: <html>(..)
testEngineConfig(org.apache.stanbol.enhancer.it.EnhancerConfigurationTest):
GET request to http://localhost:8765/enhancer/engine: no match for regexp
'<j.0:hasEngine
rdf:resource="http://localhost:.*/enhancer/engine/dbpediaLinking"/>',
content=(..)
Best regards,
Gregor
2013/11/15 Rupert Westenthaler <ru...@gmail.com>
> Hi Gregor,
>
> The folder is expected to include the following files
>
> GOSP.dat GPOS.idn OSP.dat OSPG.idn POSG.dat SPO.idn node2id.dat
> prefix2id.dat prefixIdx.idn
> GOSP.idn GSPO.dat OSP.idn POS.dat POSG.idn SPOG.dat node2id.idn
> prefix2id.idn prefixes.dat
> GPOS.dat GSPO.idn OSPG.dat POS.idn SPO.dat SPOG.idn nodes.dat
> prefixIdx.dat stats.opt
>
> As you are missing those files it indicates that the initialization of
> the TDB store is failing.
>
> IMO this looks like an issue with Jena TDB specific to your
> environment. To validate this I have creates a minimal test module [1]
> that (1) create a Jena TDB store, (2) adds an quad and (3) a Triple to
> the default Graph. If this also fails in your Environment the logs
> should be useful to file a Bug with Jena TDB.
>
> To execute the test just extract the archive and call "mvn test" in
> the module directory.
>
> best
> Rupert
>
> [1] http://dev.iks-project.eu/downloads/stanbol-launchers/tdbtest.tar.bz2
>
>
>
> On Thu, Nov 14, 2013 at 1:48 PM, Gregor Müllegger <gr...@muellegger.de>
> wrote:
> > 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 <ru...@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
> >>
>
>
>
> --
> | Rupert Westenthaler rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
>
Re: Building stanbol fails with tests for org.apache.stanbol.entityhub.indexing.source.jenatdb
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Gregor,
The folder is expected to include the following files
GOSP.dat GPOS.idn OSP.dat OSPG.idn POSG.dat SPO.idn node2id.dat
prefix2id.dat prefixIdx.idn
GOSP.idn GSPO.dat OSP.idn POS.dat POSG.idn SPOG.dat node2id.idn
prefix2id.idn prefixes.dat
GPOS.dat GSPO.idn OSPG.dat POS.idn SPO.dat SPOG.idn nodes.dat
prefixIdx.dat stats.opt
As you are missing those files it indicates that the initialization of
the TDB store is failing.
IMO this looks like an issue with Jena TDB specific to your
environment. To validate this I have creates a minimal test module [1]
that (1) create a Jena TDB store, (2) adds an quad and (3) a Triple to
the default Graph. If this also fails in your Environment the logs
should be useful to file a Bug with Jena TDB.
To execute the test just extract the archive and call "mvn test" in
the module directory.
best
Rupert
[1] http://dev.iks-project.eu/downloads/stanbol-launchers/tdbtest.tar.bz2
On Thu, Nov 14, 2013 at 1:48 PM, Gregor Müllegger <gr...@muellegger.de> wrote:
> 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 <ru...@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
>>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: Building stanbol fails with tests for org.apache.stanbol.entityhub.indexing.source.jenatdb
Posted by Gregor Müllegger <gr...@muellegger.de>.
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 <ru...@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
>
Re: Building stanbol fails with tests for org.apache.stanbol.entityhub.indexing.source.jenatdb
Posted by Rupert Westenthaler <ru...@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
On Wed, Nov 13, 2013 at 10:37 PM, Gregor Müllegger <gr...@muellegger.de> wrote:
> Hi,
>
> I just want to get started with Apache Stanbol but experience issues during
> my
> build. I get the following output:
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 26:30.064s
> [INFO] Finished at: Wed Nov 13 21:11:28 UTC 2013
> [INFO] Final Memory: 118M/390M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on
> project org.apache.stanbol.entityhub.indexing.source.jenatdb: There are
> test failures.
> [ERROR]
> [ERROR] Please refer to
> /vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports
> for the individual test results.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test
> (default-test) on project
> org.apache.stanbol.entityhub.indexing.source.jenatdb: There are test
> failures.
>
> Please refer to
> /vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports
> for the individual test results.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
> failures.
>
> Please refer to
> /vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports
> for the individual test results.
> at
> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:87)
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.writeSummary(SurefirePlugin.java:651)
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:625)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:136)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:97)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with
> the command
> [ERROR] mvn <goals> -rf
> :org.apache.stanbol.entityhub.indexing.source.jenatdb
>
>
> This seems interesting as well in the output, a bit above:
>
>
> Tests in error:
>
> testEntityDataIterable(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
> BlockMgrMapped.segmentAllocate: Segment = 0
>
> testEntityDataProvider(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
> BlockMgrMapped.segmentAllocate: Segment = 0
>
> testQuadsImport(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
> BlockMgrMapped.segmentAllocate: Segment = 0
>
> testBNodeSupport(org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest):
> BlockMgrMapped.segmentAllocate: Segment = 0
>
> Tests run: 10, Failures: 0, Errors: 4, Skipped: 0
>
>
> And here ist the content of the
> /vagrant/stanbol/entityhub/indexing/source/jenatdb/target/surefire-reports/org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest.txt
> file:
>
> http://pastebin.com/Zv4gU7Gi
>
> Unfortunatelly I don't have any idea why this might be failing :-/
>
>
> I'm using r1541504, Maven 3.0.4, Ubuntu 12.04 64bit,
> "openjdk-7-jdk" 7u25-2.3.10-1ubuntu0.12.04.2 from ubuntu repositories.
>
> I also used the `export MAVEN_OPTS="-Xmx1024M -XX:MaxPermSize=256M"` as
> explained in the docs before trying to build with `mvn install`
>
>
> Does anyone of you might know more about this?
> I'm ofcourse happy to provide more information if necessary.
>
> Thanks already in advance,
> Gregor
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen