ok, so I am running on Windows 7/64 bit and In my toplevel JENA directory, 
I ran

mvn clean
svn update
mvn install package

in ARQ, I ran into 2 issues during the ARQ tests, (see below), but I 
believe that is specific to IBM's JDK (both 6 and 7). So, I tried 
rerunning with Oracle's JDK 7 and then I run into the issue mentioned by 
Andy (i.e. tdb.TS_TDBLoader3). Now, when I run

mvn install package -DskipTests=true

I am hitting an issue building Fuseki (although the jars are created). 
This is what Maven spits out:

[INFO] --- maven-javadoc-plugin:2.8.1:jar (attach-javadocs) @ jena-fuseki 
---
[INFO] Building jar: 
D:\jfsDev\JENA\jena-fuseki\target\jena-fuseki-0.2.5-SNAPSHO
T-javadoc.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.2.1:single (create-server-assembly) @ 
jena-fu
seki ---
[INFO] Reading assembly descriptor: assembly-server.xml
[INFO] 
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] jena-parent ....................................... SUCCESS 
[4.945s]
[INFO] jena-iri .......................................... SUCCESS 
[13.147s]
[INFO] jena-core ......................................... SUCCESS 
[1:15.668s]
[INFO] jena-arq .......................................... SUCCESS 
[2:28.417s]
[INFO] jena-tdb .......................................... SUCCESS 
[2:58.328s]
[INFO] jena-fuseki ....................................... FAILURE 
[19.922s]
[INFO] apache-jena ....................................... SKIPPED
[INFO] Apache Jena ....................................... SKIPPED
[INFO] 
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] 
------------------------------------------------------------------------
[INFO] Total time: 7:20.932s
[INFO] Finished at: Tue Oct 09 17:08:38 EDT 2012
[INFO] Final Memory: 37M/259M
[INFO] 
------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.
2.1:single (create-server-assembly) on project jena-fuseki: Execution 
create-ser
ver-assembly of goal 
org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single
 failed: Unexpected internal error near index 3
[ERROR] .*\
[ERROR] ^
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutio
nException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the 
command

[ERROR]   mvn <goals> -rf :jena-fuseki

Not sure where to find more information. I don't understand the message.

Finally, this is what I get for ARQ tests when running with an IBM JDK 7:

-------------------------------------------------------------------------------
Test set: com.hp.hpl.jena.sparql.expr.TS_Expr
-------------------------------------------------------------------------------
Tests run: 1023, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.679 
sec <<< FAILURE!
nv_add_22(com.hp.hpl.jena.sparql.expr.TestNodeValueOps)  Time elapsed: 
0.005 sec  <<< ERROR!
java.lang.NullPointerException
        at 
org.apache.xerces.jaxp.datatype.AbstractDurationImpl.addDuration(Unknown 
Source)
        at 
org.apache.xerces.jaxp.datatype.AbstractDurationImpl.add(Unknown Source)
        at 
com.hp.hpl.jena.sparql.expr.nodevalue.NodeValueOps.additionNV(NodeValueOps.java:125)
        at 
com.hp.hpl.jena.sparql.expr.TestNodeValueOps.testAdd(TestNodeValueOps.java:124)
        at 
com.hp.hpl.jena.sparql.expr.TestNodeValueOps.testAdd(TestNodeValueOps.java:116)
        at 
com.hp.hpl.jena.sparql.expr.TestNodeValueOps.nv_add_22(TestNodeValueOps.java:44)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
        at java.lang.reflect.Method.invoke(Method.java:613)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:69)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:48)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
        at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
        at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:292)
        at org.junit.runners.Suite.runChild(Suite.java:128)
        at org.junit.runners.Suite.runChild(Suite.java:24)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
        at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
        at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:292)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
        at java.lang.reflect.Method.invoke(Method.java:613)
        at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
        at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
        at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
        at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
        at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
nv_sub_22(com.hp.hpl.jena.sparql.expr.TestNodeValueOps)  Time elapsed: 
0.002 sec  <<< ERROR!
java.lang.NullPointerException
        at 
org.apache.xerces.jaxp.datatype.AbstractDurationImpl.addDuration(Unknown 
Source)
        at 
org.apache.xerces.jaxp.datatype.AbstractDurationImpl.add(Unknown Source)
        at javax.xml.datatype.Duration.subtract(Unknown Source)
        at 
com.hp.hpl.jena.sparql.expr.nodevalue.NodeValueOps.subtractionNV(NodeValueOps.java:185)
        at 
com.hp.hpl.jena.sparql.expr.TestNodeValueOps.testSub(TestNodeValueOps.java:138)
        at 
com.hp.hpl.jena.sparql.expr.TestNodeValueOps.testSub(TestNodeValueOps.java:130)
        at 
com.hp.hpl.jena.sparql.expr.TestNodeValueOps.nv_sub_22(TestNodeValueOps.java:79)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
        at java.lang.reflect.Method.invoke(Method.java:613)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:69)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:48)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
        at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
        at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:292)
        at org.junit.runners.Suite.runChild(Suite.java:128)
        at org.junit.runners.Suite.runChild(Suite.java:24)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
        at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
        at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:292)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
        at java.lang.reflect.Method.invoke(Method.java:613)
        at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
        at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
        at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
        at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
        at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)



From:
Simon Helsen/Toronto/IBM@IBMCA
To:
[email protected]
Date:
10/09/2012 10:26 AM
Subject:
Re: initial test results



given that there are pre-release activities going on, I'll check if I also 

observe the issue around tdbloader3 or anything else for that matter.

Simon



From:
Simon Helsen/Toronto/IBM@IBMCA
To:
[email protected]
Date:
10/09/2012 09:37 AM
Subject:
Re: initial test results



Andy,

no, sorry, when I say internal testing, I mean running internal junit 
suites which you don't have access to as well as performance suites on top 


of client products which has the same problem. Since everyone here can run 


the regular Jena dev tests, I wasn't paying attention to them (but I 
should -> the last time I ran it I had an issue with building Fuseki, but 
I was too busy to investigate at that point)

Simon




From:
Andy Seaborne <[email protected]>
To:
[email protected]
Date:
10/06/2012 02:37 PM
Subject:
Re: initial test results



On 05/10/12 15:34, Simon Helsen wrote:
> We did some initial tests with one of our clients and there are no 
obvious
> functional regressions compared to 2.7.1. We also did not observe any
> major performance regressions and in fact, observed slight to 
significant
> write improvements (heavily depending on the scenario). We'll keep you
> posted if we find anything else. Our baseline for comparison is 2.7.1
>
> Simon
>

Excellent - thanks.

I take it you didn't run the dev tests on Windows - there's some 
bizarrity going on with tdbloader3 which I doubt is of any use to you -- 
see JENA -289 -- looks like it is a fault with the test, not the code, 
and the code is tdbloader3 specific anyway.

                 Andy







Reply via email to