Hi Bruno - sorry you are having hard time of it but it's all very
helpful information.
Thoughts, so far, inline.
On 25/10/17 22:39, Bruno P. Kinoshita wrote:
It could be normal warnings when running tests. And since you noticed it
before, I'm fine assuming it's unrelated to the issue we have
On 25/10/17 22:39, Bruno P. Kinoshita wrote:
ps : mvn clean test install -Pdev would stop in the Jena base I think,
complaining it couldn't find the jena-guava-shaded module... but mvn clean
install worked. Just for what's worth.
Use -Pbootstrap if it is a clean build, or if it tries to pic
"always" Yes, the release is the source-release.
"only" not as simple. The binary artifacts must correspond to the
source-release.
The binary artifacts going to maven central are project artifacts, and
are exposed as org.apache. It is still important. Only VOTEd material
goes to central/org
It could be normal warnings when running tests. And since you noticed it
before, I'm fine assuming it's unrelated to the issue we have right now.
First thing after getting a coffee & triggering PHP builds this morning, was to
checkout jena at 8235ee335eea114aecffd55525ad36e408a2f39b, and run `mv
As it has been seen on Ubuntu, I'm going with unintended parallel tests.
The fix is to call TC_TDB from surefire (like other modules).
Some modules may be set to find TS_* .. and again then each test suite
is sequential.
It's intermittent on OSX as well from what ajs6f reports.
Andy
On
Windows:
If we have the cause right - the test will pass!
On windows every test has a fresh, separate directory because you can't
delete mmap files while running. The effect on compact_prefixes_3 wil
be that another parallel test will not delete the shared directory.
On 25/10/17 21:28, aj..
I did notice one warning when running the tests, but most likely unrelated, and
expected for some test.
09:18:56 WARN TDB :: Location
/home/kinow/Development/java/jena/jena/jena-tdb/target/tdb-testing/DB/ was not
locked, if another JVM accessed this location simultaneous
Morning Andy,
I have access to a Windows machine at work where I can quickly start a build
later this week.
Thanks for looking into it. Decided to reply e-mails and provide more
information before leaving to the office, so that I had another chance at
running the tests in this environment where
That sounds good to me.
ajs6f
Bruno P. Kinoshita wrote on 10/25/17 10:04 PM:
Hi Andy,
I'm suspecting on either a file not being really deleted by the JVM (i.e. IOX
or Commons IO might be failing to do that), or a hidden bug somewhere else, not
really in the compaction step.
And +1 on not blo
Hi Andy,
I'm suspecting on either a file not being really deleted by the JVM (i.e. IOX
or Commons IO might be failing to do that), or a hidden bug somewhere else, not
really in the compaction step.
And +1 on not blocking the release. Perhaps we could simply mark that test with
a @Ignore + a comm
I don't understand-- I thought the release is _always and only_ the source-- the artifacts are just a convenience we
supply...?
ajs6f
Andy Seaborne wrote on 10/25/17 9:37 PM:
On 25/10/17 20:05, aj...@apache.org wrote:
Possible option: change the default Maven profile to skip TDB2 for this 3.
Just checked out the jena-3.5.0-rc1 tag and ran the complete (`mvn clean
install`) build successfully...
Mac OS 10.12.6
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode)
I didn't see the prob... love these intermittent bugs!
a
Jena_Development_Test#2766 shows the same test failure. Ubuntu.
The changes for that run were unrelated to TDB2.
So we have an intermittent failure and it suggests it is the test
harness (the test itself is entirely deterministic).
Jenkins is a bit unwell at the moment and things are very slo
On 25/10/17 20:05, aj...@apache.org wrote:
Possible option: change the default Maven profile to skip TDB2 for this
3.5.0 release?
>
We buy ourselves some time (at least until a potential 3.5.1 with a
stabilized TDB2 test regime) but we still keep TDB2 as available as
possible.
Thanks for the
Possible option: change the default Maven profile to skip TDB2 for this 3.5.0
release?
We buy ourselves some time (at least until a potential 3.5.1 with a stabilized TDB2 test regime) but we still keep TDB2
as available as possible.
I'm quite uncomfortable with releasing with the main profile
Hello Andy,
Mea culpa!! I finally tracked down my problem. The testbed was running a
slightly older version than I had thought. Now that I’m using up-to-date I’m
seeing the debug info that was added 19 Aug.
Sorry for wasting b/w,
Chris
> On Oct 23, 2017, at 4:58 PM, Chris Tomlinson
> wrote:
Bruno,
The absence of the Data-0001 is very strange. It is created for every
test in the DatabaseMgr.connectDatasetGraph call and other tests work.
I don't have access to OSX or Windows for testing and compaction is
playing around with directories and files on disk (java, portable, ...)
but
Bruno,
Thank you for running these tests.
== What to do about the 5.3.0 release
TDB2 is marked as experimental and I don't know how else to break the
deadlock of not getting used for real except by a release. I've
hammered as much as I can.
The absence of Data-0001 suggests it is a test se
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218983#comment-16218983
]
ASF subversion and git services commented on JENA-1405:
---
Commit 8b9f5
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218982#comment-16218982
]
ASF subversion and git services commented on JENA-1405:
---
Commit 59378
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218981#comment-16218981
]
ASF subversion and git services commented on JENA-1405:
---
Commit 643bd
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218984#comment-16218984
]
ASF GitHub Bot commented on JENA-1405:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/294
---
On 25/10/17 14:21, Rob Vesse wrote:
“However, no integrated benchmark-independent execution framework for these
benchmarks has yet been provided.”
My 2012 self is somewhat disappointed :(
https://github.com/rvesse/sparql-query-bm
Quite!
I don't see any references to benchmark techniques i
They have set the heap size wrong.
Andy
On 25/10/17 14:21, Rob Vesse wrote:
“However, no integrated benchmark-independent execution framework for these
benchmarks has yet been provided.”
My 2012 self is somewhat disappointed :(
https://github.com/rvesse/sparql-query-bm
Rob
On 25/10/201
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218943#comment-16218943
]
ASF GitHub Bot commented on JENA-1405:
--
Github user afs commented on the issue:
h
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/294#discussion_r146905463
--- Diff:
jena-arq/src/main/java/org/apache/jena/riot/adapters/AdapterFileManager.java ---
@@ -285,6 +286,12 @@ protected Model readModelWorker(Model model, String
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218944#comment-16218944
]
ASF GitHub Bot commented on JENA-1405:
--
Github user afs commented on a diff in the pul
Github user afs commented on the issue:
https://github.com/apache/jena/pull/294
More recently, `FmtLog.debug(logger, fmtString, args...)`.
---
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218600#comment-16218600
]
ASF GitHub Bot commented on JENA-1405:
--
Github user rvesse commented on a diff in the
“However, no integrated benchmark-independent execution framework for these
benchmarks has yet been provided.”
My 2012 self is somewhat disappointed :(
https://github.com/rvesse/sparql-query-bm
Rob
On 25/10/2017 14:08, "aj...@apache.org" wrote:
https://iswc2017.semanticweb.org/paper-70/
Github user rvesse commented on a diff in the pull request:
https://github.com/apache/jena/pull/294#discussion_r146852236
--- Diff:
jena-arq/src/main/java/org/apache/jena/riot/adapters/AdapterFileManager.java ---
@@ -285,6 +286,12 @@ protected Model readModelWorker(Model model, Str
https://iswc2017.semanticweb.org/paper-70/
is a paper in the main conference track at ISWC. It is exercising Jena 2.3.0, but I'm not sure if that version number is
for Jena/TDB or Fuseki. It is using Java 7, which makes me think they mean Fuseki 2.3.0 (Jena/TDB 3.0.0), which is still
considerab
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/294#discussion_r146827609
--- Diff:
jena-arq/src/main/java/org/apache/jena/riot/adapters/AdapterFileManager.java ---
@@ -285,6 +286,12 @@ protected Model readModelWorker(Model model, Stri
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218429#comment-16218429
]
ASF GitHub Bot commented on JENA-1405:
--
Github user ajs6f commented on a diff in the p
I think one of the tests is failing when I run
`mvn clean test install`, and also when I run the same `mvn clean test -e -X
-DforkMode=never` in debug mode in Eclipse.
The compact_prefixes_3 test method expects a directory like DB/Data-0001, but
there is only a DB folder. The methods to create
[
https://issues.apache.org/jira/browse/JENA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218371#comment-16218371
]
ASF GitHub Bot commented on JENA-1405:
--
GitHub user rvesse opened a pull request:
GitHub user rvesse opened a pull request:
https://github.com/apache/jena/pull/294
Fix and tests for possible NPE (JENA-1405)
Fixes a possible NPE in AdaptorFileManager by aligning its behaviour
with FileManager to throw NotFoundException
Adds specific tests for these cas
Rob Vesse created JENA-1405:
---
Summary: Possible NPE in AdaptorFileManager
Key: JENA-1405
URL: https://issues.apache.org/jira/browse/JENA-1405
Project: Apache Jena
Issue Type: Bug
Affects Versio
39 matches
Mail list logo
