On 15/10/12 16:50, Stephen Allen wrote:
The TestService ones might be an artifact of my network setup, which
involves a VPN, so it may just be my machine.

Could well be.  A VPN may be explicitly saying "no" to something.

Why Eclipse is different from the command line isn't obvious to me.

        Andy

-Stephen

On Mon, Oct 15, 2012 at 11:48 AM, Stephen Allen <[email protected]> wrote:
The build works OKish for me in Windows, with the exception of four tests:

For these 3, they work if I run them from within Eclipse, but from the
command line, instead of the expected SocketTimeoutException, I
instead get: java.net.SocketException Permission denied: connect
    TestService.testNumericTimeout()
    TestService.testStringTimeout()
    TestService.testStringTimeout2()


For TDBLoader3, I get BPlusTreeRewriter errors (log at bottom)
    TestTDBLoader3.test()




-Stephen


[INFO] Surefire report directory:
C:\Users\sallen\develop\Jena\trunk\jena-tdb\target\surefire-reports

-------------------------------------------------------
  T E S T S
-------------------------------------------------------
Running com.hp.hpl.jena.tdb.assembler.TS_TDBAssembler
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.375 sec
Running com.hp.hpl.jena.tdb.base.block.TS_Block
Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.904 sec
Running com.hp.hpl.jena.tdb.base.file.TS_File
Tests run: 39, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.238 sec
Running com.hp.hpl.jena.tdb.base.objectfile.TS_ObjectFile
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec
Running com.hp.hpl.jena.tdb.base.record.TS_Record
Tests run: 54, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec
Running com.hp.hpl.jena.tdb.base.recordfile.TS_RecordFile
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running com.hp.hpl.jena.tdb.graph.TS_Graph
Tests run: 67, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.469 sec
Running com.hp.hpl.jena.tdb.index.TS_Index
Tests run: 97, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.474 sec
Running com.hp.hpl.jena.tdb.lib.TS_LibTDB
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running com.hp.hpl.jena.tdb.nodetable.TS_NodeTable
Tests run: 44, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec
Running com.hp.hpl.jena.tdb.solver.TS_SolverTDB
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.049 sec
Running com.hp.hpl.jena.tdb.store.TS_Store
Tests run: 193, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.012 sec
Running com.hp.hpl.jena.tdb.sys.TS_Sys
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Running com.hp.hpl.jena.tdb.transaction.TS_Transaction
Tests run: 116, Failures: 1, Errors: 23, Skipped: 0, Time elapsed:
7.477 sec <<< FAILURE!
Running com.hp.hpl.jena.tdb.TS_Factory
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.182 sec
Running com.hp.hpl.jena.tdb.TS_Jena
Tests run: 73, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.109 sec
Running tdb.TS_TDBLoader3
11:43:34 ERROR BPlusTreeRewriter         :: **** Not the root: 1024
com.hp.hpl.jena.tdb.index.bplustree.BPTreeException
         at 
com.hp.hpl.jena.tdb.index.bplustree.BPlusTreeRewriter.packIntoBPlusTree(BPlusTreeRewriter.java:89)
         at 
org.apache.jena.tdb.store.bulkloader3.NodeTableBuilder2.buildNodeTableBPTreeIndex(NodeTableBuilder2.java:296)
         at 
org.apache.jena.tdb.store.bulkloader3.NodeTableBuilder2.close(NodeTableBuilder2.java:172)
         at tdb.tdbloader3.exec(tdbloader3.java:216)
         at arq.cmdline.CmdMain.mainMethod(CmdMain.java:101)
         at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
         at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
         at tdb.tdbloader3.main(tdbloader3.java:108)
         at tdb.TestTDBLoader3.run(TestTDBLoader3.java:120)
         at tdb.TestTDBLoader3.test(TestTDBLoader3.java:88)
         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:601)
         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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
         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.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.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:57)
         at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
         at java.lang.reflect.Method.invoke(Method.java:601)
         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)

Results :

Failed tests:
transaction_50(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB)

Tests in error:
   transaction_err_00(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_01(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_02(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_03(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_04(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_05(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_06(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_07(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_08(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_09(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_10(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\salle
n\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_01(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_02(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_03(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_04(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_05(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_06(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_07(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_08(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_09(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_10(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_11(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\
   transaction_err_12(com.hp.hpl.jena.tdb.transaction.TestTransactionTDB):
Can't expel: Active transactions for location: location:C:\Users\s
allen\develop\Jena\trunk\jena-tdb\target\tdb-testing\DB\

Tests run: 771, Failures: 1, Errors: 23, Skipped: 4




On Mon, Oct 15, 2012 at 9:57 AM, Simon Helsen <[email protected]> wrote:
a few additional notes on the fuseki build issue. I upgrade to the latest
Maven and as expected, that didn't make a difference. I also tried to
build in cygwin but that didn't help either, i.e. same error message. None
of my paths have spaces btw, something that often interferes with scripts.
For now, we can assume the problem is unique to my machine/installation.
If there is someone else here who can try to build on Windows, that would
help confirm this of course. I agree it is entirely uncritical for the
release itself



From:
Andy Seaborne <[email protected]>
To:
[email protected]
Date:
10/15/2012 05:21 AM
Subject:
Re: Preparation for Jena 2.7.4 release



Having got the SDB release out of the way, I'll start on a Jena 2.7.4

On 08/10/12 21:34, Andy Seaborne wrote:
There are a few things to be sorted before the release process can
start.

1/ JENA-333 :: javadoc production
(from the DAMLVocabulary issue)

Do we need to do anything here?
I'd rather use Java 7 (generating Java 6 class files) as before.

The two javadoc files DAMLVocabulary and DAML_OIL are zero bytes but
nothing else seems to be affected.  As DAML+OIL is all rather old, I
propose ignoring the problem.


2/ JENA-333 ; DAML+OIL

Are we going to deprecate vocabularies DAML_OIL and DAMLVocabulary?
Should anything else be deprecated as well?

My default is to deprecate the two vocabularies.


Ian's done this and also deprecated many related things.

3/ JENA-296 :: tdb.TS_TDBLoader3 test fails in Windows

Unless someone has some inspiration, I propose to simple remove the
tests.  The problem seems to be the tests can't clean up across tests in
the same run, rather than being anything to do with tdbloader3

Proposal: Avoid the test problem by building on Linux (I may find time
to crank up a pure Windows environment to take a look; not-critical)

It may be better to remove tdbloader3 from the command line
documentation on the website for the moment.  It already does require
significant tuning to get it running faster than the other loaders.

4/ There is a potential build problem with Fuseki encountered by Simon -
but it does not seem to affect me (yet :-).  Either it's windows
dependent, the incremental version of maven or bad luck.

Proposal: If it does not interfere with building, it is not critical.

                  Andy




Reply via email to