On 12/05/16 15:08, A. Soroka wrote:
This is oddly similar to the experience I had with those strange errors I
reported yesterday for Mac OS X build:
I had traced them all to o.aj.tdb.base.file.BlockAccessMapped::allocSegment
L223, where I thought it was due to totally unexpected
java.lang.OutOfMemoryError. Allocating a bigger heap did nothing to help. Now,
looking at the code with less awfully tired eyes (kids not sleeping well!), I
realize that an OOM there of all places actually represents a lack of disk
space, doesn't it? Or am I completely misunderstanding that section?
When I reported yesterday that my failed runs completed with plenty of room on
disk, that was measured after failure. If those tests are consuming the space
only while running, I might have missed it. I'll check that possibility.
The two exception messages are slightly different.
OOME (which, from memory, occurs on 32 bit systems when the segment is
out of range so (1) don't run mmap on 32 bit machines and (2) OOME is
not clear) causes:
": Offset = "+offset
so if you don't see that, it's the other one.
It's a shame the "caused by" has been lost.
What I don't undertand is why the stach trace goe to L233 when
IOException is caught, wrapped in a FileException/RuntimeException and
passed on.
It's like it is the cause exception, but the message of the wrapper.
Andy
---
A. Soroka
The University of Virginia Library
On May 12, 2016, at 9:56 AM, Osma Suominen <[email protected]> wrote:
FWIW, I tried building on a Windows 10 VM (this is the 64bit IE11/Win10 test
image from http://modern.ie that I normally use for browser testing).
I couldn't complete the build though. The JDBC TDB Driver tests seemed to
consume an enormous amount of disk space. Even though I increased the amount of
disk space available to the VM (twice - up to 80GB, of which the jena-3.1.0
folder eventually consumed about 64GB), I ran out of space in the end. I gave
up before reaching the Elephas build.
I'm probably again doing something stupid though. Someone more familiar with
doing Java development on Windows should try this.
-Osma
On 12/05/16 14:03, Stian Soiland-Reyes wrote:
Sorry, Windows 10 is not happy in building Elephas - something goes
wrong with the hadoop file system (sounds like a Hadoop bug rather
than Jena)
mvn clean install fails at:
[INFO] Apache Jena - Elephas - I/O ........................ FAILURE [09:44 min]
[INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
[INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
[INFO] Apache Jena - Distribution ......................... SKIPPED
[INFO] Apache Jena - OSGi ................................. SKIPPED
[INFO] Apache Jena - OSGi bundle .......................... SKIPPED
[INFO] Apache Jena - OSGi Karaf features .................. SKIPPED
[INFO] Apache Jena - Extras ............................... SKIPPED
[INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
[INFO] Apache Jena ........................................ SKIPPED
(In other words, all the other worked fine :)
output_04[3](org.apache.jena.hadoop.rdf.io.output.turtle.StreamedTurtleOutputTest)
Time elapsed: 0.017 sec <<< ERROR!
java.lang.NullPointerException: null
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1012)
at org.apache.hadoop.util.Shell.runCommand(Shell.java:482)
at org.apache.hadoop.util.Shell.run(Shell.java:455)
at
org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:715)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:808)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:791)
at
org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:656)
at
org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:490)
at
org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:462)
at
org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:428)
at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:908)
at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:889)
at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:786)
at
org.apache.jena.hadoop.rdf.io.output.AbstractNodeTupleOutputFormat.getRecordWriter(AbstractNodeTupleOutputFormat.java:77)
at
org.apache.jena.hadoop.rdf.io.output.AbstractNodeTupleOutputFormatTests.testOutput(AbstractNodeTupleOutputFormatTests.java:199)
at
org.apache.jena.hadoop.rdf.io.output.AbstractNodeTupleOutputFormatTests.output_04(AbstractNodeTupleOutputFormatTests.java:253)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
This is repeated across all the Elephas IO tests.
Tests run: 984, Failures: 0, Errors: 173, Skipped: 183
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: C:\Program Files\apache-maven-3.3.9\bin\..
Java version: 1.8.0_92, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_92\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
BTW, this is not the standard Windows 10, but Windows 10 Pro Insider
Preview Build 14332 - preview of what will become the "Anniersary
Edition" later this summer.
This is not a regression as I get the same error when trying to build
jena-elephas 3.0.1.
Perhaps someone with a normal Windows 10 and JDK 8 could have a go at
compiling jena-elephas? To avoid building all of 3.1.0 RC you can
always try on the 3.0.1 source release from
http://jena.apache.org/download/index.cgi as it seems the problem is
also there.
--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
[email protected]
http://www.nationallibrary.fi
