Currently on master:
All the PRs are integrated (minimal version of #297 - tests are much
faster, with a build taking about 12-13 minutes).
It's run a couple of times on Apache jenkins as well.
If anyone gets the chance to run from master on Windows or OSX, that
would be great.
[
https://issues.apache.org/jira/browse/JENA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222769#comment-16222769
]
Andy Seaborne commented on JENA-1407:
-
A comparison of the changes:
The machine is quad-core with
[
https://issues.apache.org/jira/browse/JENA-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1406.
-
Resolution: Fixed
Fix Version/s: Jena 3.4.0
> Fix TDB2 TestDatabaseOps.compact_prefixes_3
[
https://issues.apache.org/jira/browse/JENA-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1409.
-
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.4.0
1 and 2 are
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/295
---
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/298
---
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/296
---
There are test problems with TestProcessFileLock (on windows,
consistently) and TestDatabaseOps (intermittent but seems to like
picking on Bruno).
There a couple of other small PRs for fixes which look safe as well.
PR #294 AdapterFileManager fix
(Rob - JENA-1405 can be resolved?)
PR #297
[
https://issues.apache.org/jira/browse/JENA-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1638#comment-1638
]
ASF GitHub Bot commented on JENA-1409:
--
GitHub user afs opened a pull request:
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/298
JENA-1409: ProcessFileLock
- Fix testing for MS Windows.
- Close files when a lock is finished with.
You can merge this pull request into a Git repository by running:
$ git pull
There isn't sufficient confidence in this release candidate and there
quite a few PRs.
I'll send out a plan for RC2 soon. These will be the only changes made
for RC2 so any checking work done elsewhere isn't invalidated.
Osma - thank you for voting.
Andy
[
https://issues.apache.org/jira/browse/JENA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1601#comment-1601
]
ASF GitHub Bot commented on JENA-1407:
--
Github user afs commented on the issue:
[
https://issues.apache.org/jira/browse/JENA-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1410:
Description:
When a persistent dataset is deleted from Fuseki WEB GUI, the dataset folder in
[
https://issues.apache.org/jira/browse/JENA-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1600#comment-1600
]
Andy Seaborne commented on JENA-1410:
-
The code in ActionDatasets.execDeleteItem appears to have delete
Github user afs commented on the issue:
https://github.com/apache/jena/pull/297
From the documentation, the default mode of Surefire is that
`` is count-per-core.
{noformat}
perCoreThreadCount (Default: true)
(JUnit 4.7 provider) Indicates that threadCount,
[
https://issues.apache.org/jira/browse/JENA-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1410:
Summary: Removing persistent dataset in Fuseki 3.4.0 doesn't work (was:
Removig persitent dataset
Hi,
As I've promised earlier I took TDB2 for a little test drive, using the
3.5.0rc1 builds.
I tested two scenarios: A server running Fuseki, and command line tools
operating directly on a database directory.
1. Server running Fuseki
First the server (running as a VM). Currently I've been
David Molina Estrada created JENA-1410:
--
Summary: Removig persitent dataset in Fuseki 3.4.0 doen't work
Key: JENA-1410
URL: https://issues.apache.org/jira/browse/JENA-1410
Project: Apache Jena
[
https://issues.apache.org/jira/browse/JENA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221942#comment-16221942
]
ASF GitHub Bot commented on JENA-1407:
--
Github user rvesse commented on the issue:
Github user rvesse commented on the issue:
https://github.com/apache/jena/pull/297
I have now changed this to dynamically set test parallelism to use 50% of
available cores
---
[
https://issues.apache.org/jira/browse/JENA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221929#comment-16221929
]
ASF GitHub Bot commented on JENA-1407:
--
Github user rvesse commented on the issue:
Github user rvesse commented on the issue:
https://github.com/apache/jena/pull/297
Parallelism of 2 gives similar benefits. I have a quad core machine
personally.
One possible approach is to use the `build-helper:cpu-count` plugin -
+1
I've built the RC twice on Ubuntu 16.04: one full build and one using
-Pdev. I didn't encounter the build problems others have seen. I'll let
others decide whether they are serious enough to warrant another RC.
I've done some TDB2 testing, will write about that in a separate message.
23 matches
Mail list logo
